Digital electronic invoice generation method and device, electronic equipment and storage medium
By obtaining invoice plane code and business permissions, the digital invoice issuance process is automated, which solves the problem of low efficiency invoice issuance, simplifies operational steps and improves efficiency and safety.
Patent Information
- Application Number
- CN202411364884.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2024-12-31
AI Technical Summary
The issuance process of digital invoices is cumbersome, resulting in low issuance efficiency, and enterprises need to spend a lot of time understanding and operating complicated steps.
By obtaining the digital invoice issuance request of the business object, obtaining the invoice plane code in response, using the flat code to obtain the invoice scan page, the scanning code page triggers the subsequent issuance process, ensuring user access security, and obtaining permissions generated numbers on the business authentication page Electric invoices are issued automatically.
The issuance process of digital invoices has been simplified, the issuance efficiency has been improved, and the time period required for enterprises to become familiar with the platform functions has been reduced, ensuring the security of business data and operational flexibility.
Smart Images
Figure CN119228460A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of financial technology, and in particular to a method and device for generating digital invoices, an electronic device and a storage medium. Background Art
[0002] Digital invoices are fully digitalized electronic invoices that can be used as a transaction voucher to ensure the transparency of transactions. For example, after a company purchases insurance, it needs to issue a digital invoice so that it can use the digital invoice for subsequent insurance claims procedures. However, the process of issuing digital invoices is cumbersome, which prolongs the invoicing cycle and leads to low efficiency in issuing digital invoices. Summary of the invention
[0003] The main purpose of the embodiments of the present application is to propose a method and device for generating digital electrical invoices, an electronic device and a storage medium, aiming to improve the efficiency of issuing digital electrical invoices.
[0004] To achieve the above-mentioned purpose, a first aspect of an embodiment of the present application proposes a method for generating a digital invoice, the method comprising:
[0005] Get the digital invoice issuance request of the business object;
[0006] In response to the digital invoice issuance request, obtaining the invoice plane code;
[0007] Obtaining an invoice scanning page according to the invoice plane code;
[0008] Scan the invoice code scanning page to obtain the business authentication page of the business object;
[0009] Obtaining the business authority of the business object on the business authentication page;
[0010] A digital invoice for the business object is generated according to the business authority.
[0011] In some embodiments, the step of obtaining the invoice plane code in response to the digital invoice issuance request includes:
[0012] In response to the digital invoice issuance request, obtaining an object database index of the business object from a preset database;
[0013] The digital invoice issuance request and the object database index are concatenated to obtain target invoice data;
[0014] The plane code generation interface is called according to the target invoice data to obtain the invoice plane code.
[0015] In some embodiments, the method is applied to a business application end of a digital invoice issuance system, the digital invoice issuance system further comprising a business service end, and the step of obtaining an object database index of a business object from a preset database in response to the digital invoice issuance request comprises:
[0016] In response to the digital invoice issuance request, obtaining original business data of the business object;
[0017] Sending the original business data to the business service end;
[0018] Receiving encrypted business data obtained by encrypting the original business data by the business service end;
[0019] The encrypted business data is stored in the preset database, and the object database index of the business object is obtained.
[0020] In some embodiments, the method is applied to a business application end of a data invoice issuance system, the data invoice issuance system further includes a business service end, and the step of obtaining an invoice scanning code page according to the invoice plane code includes:
[0021] Sending the invoice plane code to the business service end;
[0022] Receive the invoice scanning page returned by the business service end according to the invoice plane code; the invoice scanning page is obtained by the business service end integrating the invoice plane code and a preset web page creation file.
[0023] In some embodiments, generating the digital invoice of the business object according to the business authority includes:
[0024] Jump to the invoice issuance page according to the business authority;
[0025] A digital invoice for the business object is generated on the invoice issuance page.
[0026] In some embodiments, generating the digital invoice of the business object on the invoice issuance page includes:
[0027] Obtaining the object database index of the business object through the invoice issuance page;
[0028] Acquire the business data of the business object from a preset database according to the object database index to obtain target business data;
[0029] Filling the target business data into the invoice issuance page to obtain a candidate issuance page;
[0030] A digital invoice for the business object is issued on the candidate issuance page.
[0031] In some embodiments, acquiring the business data of the business object from the preset database according to the object database index to obtain the target business data includes:
[0032] Performing a limited-period verification on the object database index to obtain a target object index;
[0033] The business data of the business object is acquired from the preset database according to the target object index to obtain the target business data.
[0034] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application provides a digital invoice generation device, the device comprising:
[0035] The request acquisition module is used to obtain the digital invoice issuance request of the business object;
[0036] A response module, used for responding to the digital invoice issuance request and obtaining the invoice plane code;
[0037] A page acquisition module, used to acquire an invoice scanning code page according to the invoice plane code;
[0038] A scanning module, used to scan the invoice code scanning page to obtain the business authentication page of the business object;
[0039] A permission acquisition module, used to obtain the business permission of the business object on the business authentication page;
[0040] A generation module is used to generate a digital invoice for the business object according to the business authority.
[0041] To achieve the above objectives, a third aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method described in the first aspect is implemented.
[0042] To achieve the above-mentioned purpose, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in the first aspect is implemented.
[0043] The digital invoice generation method, digital invoice generation device, electronic device and computer-readable storage medium proposed in the embodiment of the present application, by obtaining the digital invoice issuance request of the business object, to issue the digital invoice based on the digital invoice issuance request, so as to facilitate the management and control of the digital invoice issuance process. In response to the digital invoice issuance request, the invoice plane code is obtained to link to the web page associated with the digital invoice issuance process based on the invoice plane code, without having to know the detailed process of digital invoice issuance in advance, avoiding the cumbersome data invoice issuance operation. According to the invoice plane code, the invoice scanning page is obtained to trigger the subsequent digital invoice issuance process by using the invoice scanning page. The invoice scanning page is scanned to obtain the business authentication page of the business object, so as to use the business authentication page to ensure that the user's page access is safe. In order to ensure that the business object has the authority to issue digital invoices, the business authority of the business object is obtained on the business authentication page, and the digital invoice of the business object is generated according to the business authority, which can realize the automatic issuance of digital invoices and improve the efficiency of digital invoice issuance. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 It is a flow chart of a method for generating a digital electricity invoice provided in an embodiment of the present application;
[0045] Figure 2 yes Figure 1 Flow chart of step S120 in FIG.
[0046] Figure 3 yes Figure 2 Flow chart of step S210 in FIG.
[0047] Figure 4 yes Figure 1 Flow chart of step S130 in FIG.
[0048] Figure 5 yes Figure 1 Flow chart of step S160 in FIG.
[0049] Figure 6 yes Figure 5 Flow chart of step S520 in FIG.
[0050] Figure 7 yes Figure 6 Flow chart of step S620 in FIG.
[0051] Figure 8 It is a structural schematic diagram of a digital invoice generating device provided in an embodiment of the present application;
[0052] Fig. 9 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION
[0053] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0054] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0055] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.
[0056] Digital invoices are fully digitalized electronic invoices that can be used as a transaction voucher to ensure the transparency of transactions. For example, after a company purchases insurance, it needs to issue a digital invoice so that it can use the digital invoice for subsequent insurance claims procedures. However, the process of issuing digital invoices is cumbersome, which prolongs the invoicing cycle and leads to low efficiency in issuing digital invoices.
[0057] Based on this, the embodiments of the present application provide a method for generating a digital electrical invoice, a device for generating a digital electrical invoice, an electronic device and a computer-readable storage medium, aiming to improve the efficiency of issuing digital electrical invoices.
[0058] The digital electrical invoice generation method, digital electrical invoice generation device, electronic device and computer-readable storage medium provided in the embodiments of the present application are specifically explained through the following embodiments. First, the digital electrical invoice generation method in the embodiments of the present application is described.
[0059] The digital electricity invoice generation method provided in the embodiment of the present application relates to the field of financial technology technology. The digital electricity invoice generation method provided in the embodiment of the present application can be applied to a terminal, can also be applied to a server side, and can also be software running in a terminal or a server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the digital electricity invoice generation method, etc., but is not limited to the above forms.
[0060] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.
[0061] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.
[0062] Figure 1 This is an optional flowchart of the method for generating a digital invoice provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S110 to S160.
[0063] Step S110, obtaining a digital invoice issuance request of a business object;
[0064] Step S120, in response to the digital invoice issuance request, obtaining the invoice plane code;
[0065] Step S130, obtaining the invoice scanning page according to the invoice plane code;
[0066] Step S140, scanning the invoice code scanning page to obtain the business authentication page of the business object;
[0067] Step S150, obtaining the business rights of the business object on the business authentication page;
[0068] Step S160, generating a digital invoice for the business object according to the business authority.
[0069] Steps S110 to S160 shown in the embodiment of the present application trigger the jump of the page based on the invoice plane code, thereby automating the digital electronic invoice issuance process without the need to previously understand the cumbersome steps involved in the digital electronic invoice issuance, thereby simplifying the digital electronic invoice issuance process and improving the efficiency of digital electronic invoice issuance.
[0070] In step S110 of some embodiments, the business object is an object that needs to issue a digital invoice in the business transaction process, such as an insurance policy for insurance business, an order for financial product recommendation business, etc. After the enterprise conducts a business transaction on the business application end, it needs to register the enterprise and understand the platform functions of the business application end in detail, find the invoicing entry of the business object to issue a digital invoice. However, the time period required to familiarize yourself with the platform functions and operation processes is long, resulting in a reduced efficiency in issuing digital invoices. In order to improve the efficiency of issuing digital invoices, the embodiment of the present application combines the business application end, the business service end and the digital invoice issuing end to build a data invoice issuing system, open up the channel for issuing digital invoices online, and use the business application end as a mobile client platform for issuing digital invoices online. The business service end is the background server end of the business application end, which is used to process the business transaction data involved in the business application end. The digital invoice issuing end is used to issue digital invoices. The business application end is triggered at the end of the business transaction process, creates a business object, and generates a link to the invoicing page of the business object. In response to clicking on the link to the invoicing page, a request for issuing a digital invoice is obtained. The digital invoice issuance request is information sent by the business application end to the digital invoice issuance end to request the issuance of a digital invoice.
[0071] In order to improve the efficiency of digital invoice issuance by enterprises, the business application terminal responds to the digital invoice issuance request, generates a matrix barcode symbol, and obtains the invoice plane code.
[0072] See also Figure 2 In some embodiments, step S120 may include but is not limited to steps S210 to S230:
[0073] Step S210, in response to the digital invoice issuance request, obtaining an object database index of the business object from a preset database;
[0074] Step S220, concatenating the digital invoice issuance request and the object database index to obtain target invoice data;
[0075] Step S230, calling the plane code generation interface according to the target invoice data to obtain the invoice plane code.
[0076] In step S210 of some embodiments, the preset database is a redis database, which is a high-performance key-value storage system based on memory and stores data information provided by users in the form of key-value pairs. The digital invoice issuance request is responded to, the key of the business object is obtained from the redis database, and the key is used as the object information identifier of the business object to obtain the object database index.
[0077] In step S220 of some embodiments, the target invoice data is obtained by splicing the object database index to the digital invoice issuance request.
[0078] In step S230 of some embodiments, the flat code generation interface is called by means of an open application programming interface (Open API), the target invoice data is passed to the flat code generation interface, the target invoice data is converted into an ASCII string consisting of 64 printable characters using a base64 encoding method, and the string is converted into a two-dimensional image to obtain an invoice flat code. The flat code generation interface is an application program interface for generating flat codes. By generating flat codes through object database indexes rather than specific data content of business objects, it is possible to avoid sending customer information to an external flat code generation interface, thereby ensuring the security of customer information, while reducing the amount of data that needs to be sent, making the image of the invoice flat code clearer and increasing the probability of successful page jumps.
[0079] Through the above steps S210 to S230, the invoice plane code can be obtained, so as to automatically jump to the web page based on the invoice plane code to realize the issuance of digital electronic invoices without having to know the cumbersome operation process involved in the issuance of digital electronic invoices in advance.
[0080] See also Figure 3 In some embodiments, the digital invoice generation method is applied to the business application end of the digital invoice issuance system, and the digital invoice issuance system also includes a business service end. Step S210 may include but is not limited to steps S310 to S340:
[0081] Step S310, in response to the digital invoice issuance request, obtaining the original business data of the business object;
[0082] Step S320, sending the original business data to the business service end;
[0083] Step S330, receiving encrypted business data obtained by encrypting the original business data by the business server;
[0084] Step S340: store the encrypted business data into a preset database, and obtain an object database index of the business object.
[0085] In step S310 of some embodiments, in response to the digital invoice issuance request, key information of the business object required for issuing the digital invoice on the business application end webpage is obtained to obtain the original business data. The original business data includes object information of the business object, such as the policy number of the insurance policy, the order number of the order, contact information, account information, etc.
[0086] In step S320 of some embodiments, in order to facilitate data processing and storage of the original business data and ensure the security of the original business data, the original business data is sent to the business service end. The business service end encrypts the original business data using the AES encryption algorithm to obtain encrypted business data, and sends the encrypted business data to the business application end.
[0087] The original business data involves different types of data such as personal identity information and financial information. Different types of data require different encryption levels. For example, the encryption level required for financial information is higher than that for personal identity information. In order to better protect data security and meet the diversified data encryption requirements, the business service end can classify the original business data to obtain multiple types of sub-business data. The encryption level of each type of sub-business data is obtained respectively, the key length is obtained according to the encryption level, the key is generated according to the key derivation function and the key length, the encryption mode pre-configured in the configuration file is read, and the sub-business data is encrypted according to the encryption mode and the key until all types of sub-business data are encrypted to obtain encrypted business data. The encryption level includes level 1 encryption, level 2 encryption or level 3 encryption. The encryption degree of level 1 encryption, level 2 encryption and level 3 encryption increases in turn, and the corresponding key length increases in turn. The key lengths of level 1 encryption, level 2 encryption and level 3 encryption are 128 bits, 192 bits and 256 bits respectively. The encryption mode includes electronic codebook mode, cipher block chaining mode and counter mode. In order to further improve the security of the original business data, the key management system can be used to store the key and automatically update the key regularly.
[0088] In step S330 of some embodiments, the business application end receives encrypted business data sent by the business service end.
[0089] In step S340 of some embodiments, the encrypted business data is stored in the redis database. The redis database assigns a key and a validity period of the key to the business object, uses the key as the object database index of the business object, and uses the encrypted business data as the value associated with the key. By storing business data in key-value pairs, the database can store business data of different data structure types and improves the efficiency of business data access.
[0090] In order to improve the storage efficiency of encrypted business data and the storage capacity of the database to meet the growing data volume and access requirements, the business application end can obtain the remaining storage capacity of the redis database and the data capacity of the encrypted business data in advance. If the remaining storage capacity is less than the data capacity, the number of requests for the current digital invoice issuance request is obtained. If the number of requests is greater than or equal to the preset request threshold, the number of redis databases is increased to horizontally expand the redis database so that the redis database can handle a large number of concurrent storage requests and store the encrypted business data in the expanded redis database. The number of redis databases is obtained by the ratio of the number of requests for the current digital invoice issuance request to the maximum number of requests for the digital invoice issuance request that a single redis database can handle. The preset request threshold is greater than the maximum number of requests for the digital invoice issuance request that a single redis database can handle. If the number of requests is less than the preset request threshold, the data capacity is subtracted from the remaining storage capacity to obtain the difference capacity, and the difference capacity is added to the redis database to vertically expand the redis database. If the remaining storage capacity is greater than or equal to the data capacity, the capacity of the redis database is maintained unchanged.
[0091] Through the above steps S310 to S340, the object database index can be obtained on the basis of ensuring the security of business data, so as to generate a flat code based on the object database index.
[0092] See also Figure 4 In some embodiments, step S130 may include but is not limited to steps S410 to S420:
[0093] Step S410, sending the invoice plane code to the business service end;
[0094] Step S420, receiving the invoice scanning page returned by the business server according to the invoice plane code; the invoice scanning page is obtained by the business server integrating the invoice plane code and the preset web page creation file.
[0095] In step S410 of some embodiments, the invoice plane code is used to link to a specific web page, and the guidance information cannot be displayed intuitively to the user. In order to provide additional guidance information such as plane code expiration time, operation guidance information, etc., and increase the accessibility and readability of the page, the invoice plane code is sent to the business service end. The business service end integrates the invoice plane code and the web page creation file through the freemarker framework to create a web page, obtain the invoice code scanning page, and send the invoice code scanning page to the business application end. The web page creation file uses HyperText Markup Language (HTML) to describe the structure and content of the web page. It is a poster file generated by tags, cascading style sheets and JavaScript code. Additional guidance information can be dynamically filled in the poster file. The invoice plane code is spliced onto the poster to form a plane code poster and obtain an invoice code scanning page.
[0096] In step S420 of some embodiments, the business application end receives the invoice scanning page returned by the business service end based on the invoice plane code, so as to use the invoice scanning page to realize the jump of the web page and provide additional guidance information.
[0097] Through the above steps S410 to S420, the invoice code can be interpreted through the invoice scanning page without scanning the invoice code, thereby improving the accessibility and readability of the web page.
[0098] In step S140 of some embodiments, the invoice code scanning page is scanned, and the page jumps to the business authentication page of the business object. The business object is authenticated through the business authentication page to ensure that the digital invoice can be issued for the business object.
[0099] In step S150 of some embodiments, a verification code is entered on the business authentication page, the business object is bound through the verification code, and the business authority to issue digital invoices to the business object is obtained. The verification code is a transaction verification code assigned to the business object by the business service end after the transaction business is completed by the business application end, such as the verification code of the insurance policy, the verification code of the product order, etc. Specifically, the verification code is entered on the business authentication page and submitted to the business service end. The verification code entered on the business authentication page is compared with the verification code stored on the business service end. If the two are the same, the verification is successful, and the business application end is allowed to bind the business object. If the two are different, the verification fails, and the business application end is not allowed to bind the business object.
[0100] See also Figure 5 In some embodiments, step S160 may include but is not limited to steps S510 to S520:
[0101] Step S510, jump to the invoice issuance page according to the business authority;
[0102] Step S520: Generate a digital invoice for the business object on the invoice issuance page.
[0103] In step S510 of some embodiments, after obtaining the business authority, the process directly jumps to the invoice issuance page to issue a digital invoice.
[0104] In step S520 of some embodiments, an invoice issuance task is generated on the invoice issuance page, and the invoice issuance task is sent to the digital invoice issuance end. The digital invoice issuance end issues a digital invoice for the business object and returns the digital invoice to the business application end.
[0105] Through the above steps S510 to S520, not only the security of the digital invoice issuance process can be guaranteed, but also the time spent on familiarizing with the business application functions is saved, thereby improving the efficiency of digital invoice issuance.
[0106] See also Figure 6 In some embodiments, step S520 may include but is not limited to steps S610 to S640:
[0107] Step S610, obtaining the object database index of the business object through the invoice issuance page;
[0108] Step S620, acquiring business data of the business object from a preset database according to the object database index to obtain target business data;
[0109] Step S630, filling the target business data into the invoice issuance page to obtain a candidate issuance page;
[0110] Step S640, issuing a digital invoice for the business object on the candidate issuance page.
[0111] In step S610 of some embodiments, the invoice plane code is generated by the object database index. When jumping to the invoice issuance page, the invoice issuance page will obtain the object database index of the business object.
[0112] In step S620 of some embodiments, a request is made to the redis database to obtain the encrypted business data associated with the object database index according to the object database index to obtain the target business data.
[0113] In step S630 of some embodiments, the target business data is automatically loaded into the invoice issuance page to obtain a candidate issuance page.
[0114] In step S640 of some embodiments, a page check is performed on the candidate issuance page to obtain a target issuance page, and in response to a page confirmation instruction for the target issuance page, an invoice issuance task is generated according to the page confirmation instruction, the invoice issuance task is sent to the digital invoice issuance end, and the digital invoice returned by the digital invoice issuance end according to the invoice issuance task is received. Specifically, the target business data of the candidate issuance page is checked. If the target business data is correct, the candidate issuance page is used as the target issuance page, the confirmation button of the target issuance page is clicked, a page confirmation instruction is generated, and a request is made to the digital invoice issuance end to issue the digital invoice of the business object according to the page confirmation instruction. If the target business data is wrong, the target business data is modified on the candidate issuance page, and the updated candidate issuance page is used as the target issuance page. When the generation speed of the invoice issuance task is greater than the processing speed, the digital invoice issuance end will receive a large number of invoice issuance tasks within a period of time. In order to improve the response efficiency of the digital invoice issuance end to the request, the invoice issuance task can be temporarily stored in the message queue.
[0115] Through the above steps S610 to S640, after completing the transaction, you only need to check the page information on the business application end to issue a digital invoice, which can be applied to a variety of business channels, greatly improving the efficiency and flexibility of digital invoice issuance.
[0116] See also Figure 7 In some embodiments, step S620 may include but is not limited to steps S710 to S720:
[0117] Step S710, performing a limited-period check on the object database index to obtain the target object index;
[0118] Step S720: acquiring business data of the business object from a preset database according to the target object index to obtain target business data.
[0119] In step S710 of some embodiments, a request is made to the redis database to obtain encrypted business data according to the object database index. To ensure the security of the encrypted business data acquisition process, the redis database verifies the validity period of the object database index. If the object database index has not expired, the object database index is used as the target object index. If the object database index has expired, a prompt message indicating that the invoice plane code has expired is returned to the business application end.
[0120] In step S720 of some embodiments, encrypted business data of a business object associated with a target object index is acquired from a preset database to obtain target business data.
[0121] In the above steps S710 to S720, the security of business data can be ensured through validity period verification, thereby ensuring the security of the digital invoice issuance process.
[0122] After purchasing insurance, companies need to issue digital invoices as transaction vouchers. In the process of issuing digital invoices, companies need to register on the business application side in advance, familiarize themselves with the platform functions of the business application side, and find the invoicing portal to issue digital invoices. The entire process takes a long time, resulting in low efficiency in issuing digital invoices. In addition, most companies do not want to spend a lot of time understanding the cumbersome operating steps involved in the process of issuing digital invoices, which increases the difficulty of issuing digital invoices for insurance policies.
[0123] In order to improve the efficiency of enterprises in issuing digital invoices and reduce the difficulty of issuing digital invoices for insurance policies, the embodiment of the present application combines the business application end, the application service end and the data invoice issuing end to open up the channel for issuing digital invoices online. The digital invoice generation method of the embodiment of the present application includes: triggered by the success of the insurance policy transaction, the business application end obtains the policy data of the insurance policy, and the policy data includes the policy number, contact information and account information. Send the policy data to the business service end, encrypt the policy data through the business service end, obtain the encrypted policy data, and send the encrypted policy data to the business application end. The business application end receives the encrypted policy data sent by the business service end, stores the encrypted policy data in the redis database, and obtains the database index of the policy. The business application end obtains the invoice issuance request, the invoice issuance request includes the policy number, obtains the database index from the redis database according to the policy number, and obtains the invoice page link after splicing the database index to the invoice issuance request. Call the flat code generation interface to generate the flat code of the invoice page link, obtain the invoice flat code, and send the invoice flat code to the business service end. The business server calls the freemarker framework to integrate the HTML file and the invoice flat code to obtain the invoice scanning page. The business application receives the invoice scanning page sent by the business server, scans the invoice scanning page, logs in to the business application with one click, and jumps to the business authentication page. The business authentication page includes a list of all the insurance policies to be invoiced by the enterprise. Enter the verification code of a certain policy in the insurance policy list on the business authentication page, bind the policy, and implement a one-to-one invoicing method. Enter the verification code of all insurance policies in the insurance policy list on the business authentication page, bind all insurance policies, and implement a one-to-many invoicing method, making the digital electricity invoice issuance operation flexible and changeable. By binding the insurance policy, you can obtain all the business permissions of the insurance policy. After the insurance policy is successfully bound, jump to the invoice issuance page, which includes a database index. A request is initiated to the redis database based on the database index. The redis database verifies the validity period of the database index. If the database index is not expired, the encrypted business data associated with the database index is sent to the business application. The business application end automatically loads the encrypted business data into the invoice issuance page, generates an invoice issuance task, and sends the invoice issuance task to the digital invoice issuance end to issue the digital invoice for the insurance policy. After the digital invoice is asynchronously issued successfully, a notification is sent to the business application end so that the business application end can download the digital invoice based on the notification information. If the database index expires, a prompt message is sent to the business application end that the invoice plane code has expired.
[0124] It should be noted that if the business application end has not registered the enterprise, it can directly generate a universal invoice plane code according to the digital electricity invoice issuance request, and receive the invoice scanning page generated by the business service end according to the invoice plane code and HTML file. Scan the invoice scanning page to obtain the business authentication page, perform enterprise registration authentication on the business authentication page, enter the policy data and verification code of the insurance policy, and jump to the invoice issuance page. After entering the policy data, the business application end can send the policy data to the business service end for encryption, and store the encrypted policy data in the redis database to facilitate the repeated issuance of digital electricity invoices.
[0125] Through the above-mentioned digital invoice generation method, enterprises can issue digital invoices required for insurance policies on the business application side, opening up a new mode of issuing digital invoices on the online client side. At the same time, it can help enterprises save a lot of time to understand the business application side. Enterprises only need to check information to issue invoices, which improves the efficiency of issuing digital invoices. Through authentication operations, enterprises that are not subject to the insurance policy cannot bind the insurance policy to prevent unauthorized use. By encrypting business data and setting the validity period, the security of the digital invoice issuance process is guaranteed.
[0126] See also Figure 8 The embodiment of the present application also provides a digital invoice generation device, which can implement the above-mentioned digital invoice generation method, and the device includes:
[0127] The request acquisition module 810 is used to acquire the digital invoice issuance request of the business object;
[0128] A response module 820 is used to respond to the digital invoice issuance request and obtain the invoice plane code;
[0129] The page acquisition module 830 is used to acquire the invoice scanning code page according to the invoice plane code;
[0130] The scanning module 840 is used to scan the invoice code scanning page to obtain the business authentication page of the business object;
[0131] The authority acquisition module 850 is used to obtain the business authority of the business object on the business authentication page;
[0132] The generation module 860 is used to generate a digital invoice for a business object according to the business authority.
[0133] In some embodiments, the digital invoice generating device is further used to:
[0134] In response to a digital invoice issuance request, obtaining an object database index of a business object from a preset database;
[0135] Connect the digital invoice issuance request and the object database index to obtain the target invoice data;
[0136] Call the flat code generation interface according to the target invoice data to obtain the invoice flat code.
[0137] In some embodiments, the digital invoice generating device is further used to:
[0138] Responding to the digital invoice issuance request, obtaining the original business data of the business object;
[0139] Send the original business data to the business server;
[0140] The encrypted business data obtained by receiving the original business data encrypted by the business server;
[0141] The encrypted business data is stored in a preset database, and an object database index of the business object is obtained.
[0142] In some embodiments, the digital invoice generating device is further used to:
[0143] Send the invoice flat code to the business server;
[0144] The receiving business server returns the invoice code scanning page based on the invoice code. The invoice code scanning page is obtained by integrating the invoice code and the preset web page creation file by the business server.
[0145] In some embodiments, the digital invoice generating device is further used to:
[0146] Jump to the invoice issuance page according to business permissions;
[0147] Generate digital invoices for business objects on the invoice issuance page.
[0148] In some embodiments, the digital invoice generating device is further used to:
[0149] Obtain the object database index of the business object through the invoice issuance page;
[0150] Obtain the business data of the business object from the preset database according to the object database index to obtain the target business data;
[0151] Fill the target business data into the invoice issuance page to obtain a candidate issuance page;
[0152] Issue digital invoices for business objects on the candidate invoicing page.
[0153] In some embodiments, the digital invoice generating device is further used to:
[0154] Perform a limited-period check on the object database index to obtain the target object index;
[0155] The business data of the business object is obtained from a preset database according to the target object index to obtain the target business data.
[0156] The specific implementation of the digital invoice generation device is basically the same as the specific implementation of the above-mentioned digital invoice generation method, and will not be repeated here.
[0157] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned digital electricity invoice generation method when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.
[0158] See also Fig. 9 , Fig. 9 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:
[0159] The processor 910 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;
[0160] The memory 920 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 920 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 920, and the processor 910 calls and executes the digital invoice generation method of the embodiment of this application;
[0161] Input / output interface 930, used to implement information input and output;
[0162] Communication interface 940, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);
[0163] bus 950 , which transmits information between the various components of the device (e.g., processor 910 , memory 920 , input / output interface 930 , and communication interface 940 );
[0164] The processor 910 , the memory 920 , the input / output interface 930 , and the communication interface 940 are connected to each other in communication within the device via a bus 950 .
[0165] The embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned digital invoice generation method is implemented.
[0166] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0167] The digital electronic invoice generation method and device, electronic device and storage medium provided in the embodiments of the present application trigger the jump of the page based on the invoice plane code, thereby automating the digital electronic invoice issuance process without the need to previously understand the cumbersome steps involved in the digital electronic invoice issuance, thereby simplifying the digital electronic invoice issuance process and improving the efficiency of digital electronic invoice issuance.
[0168] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0169] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.
[0170] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0171] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.
[0172] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0173] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0174] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0175] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0176] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0177] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.
[0178] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.
Claims
1. A method for generating digital invoices, characterized in that: The method comprises: Get the digital invoice issuance request of the business object; In response to the digital invoice issuance request, obtaining the invoice plane code; Obtaining an invoice scanning page according to the invoice plane code; Scan the invoice code scanning page to obtain the business authentication page of the business object; Obtaining the business authority of the business object on the business authentication page; A digital invoice for the business object is generated according to the business authority.
2. The method according to claim 1, characterized in that The step of obtaining the invoice plane code in response to the digital invoice issuance request includes: In response to the digital invoice issuance request, obtaining an object database index of the business object from a preset database; The digital invoice issuance request and the object database index are concatenated to obtain target invoice data; The plane code generation interface is called according to the target invoice data to obtain the invoice plane code.
3. The method according to claim 2, characterized in that The method is applied to the business application end of the digital invoice issuance system, and the digital invoice issuance system also includes a business service end. The method responds to the digital invoice issuance request and obtains the object database index of the business object from the preset database, including: In response to the digital invoice issuance request, obtaining original business data of the business object; Sending the original business data to the business service end; Receiving encrypted business data obtained by encrypting the original business data by the business service end; The encrypted business data is stored in the preset database, and the object database index of the business object is obtained.
4. The method according to claim 1, characterized in that The method is applied to the business application end of the data invoice issuance system, and the data invoice issuance system also includes a business service end. The invoice scanning page is obtained according to the invoice plane code, including: Sending the invoice plane code to the business service end; Receive the invoice scanning page returned by the business service end according to the invoice plane code; the invoice scanning page is obtained by the business service end integrating the invoice plane code and a preset web page creation file.
5. The method according to any one of claims 1 to 4, characterized in that: The step of generating the digital invoice for the business object according to the business authority includes: Jump to the invoice issuance page according to the business authority; A digital invoice for the business object is generated on the invoice issuance page.
6. The method according to claim 5, characterized in that Generating the digital invoice for the business object on the invoice issuance page includes: Obtaining the object database index of the business object through the invoice issuance page; Acquire the business data of the business object from a preset database according to the object database index to obtain target business data; Filling the target business data into the invoice issuance page to obtain a candidate issuance page; A digital invoice for the business object is issued on the candidate issuance page.
7. The method according to claim 6, characterized in that The acquiring the business data of the business object from the preset database according to the object database index to obtain the target business data includes: Performing a limited-period verification on the object database index to obtain a target object index; The business data of the business object is acquired from the preset database according to the target object index to obtain the target business data.
8. A digital invoice generation device, characterized in that: The device comprises: The request acquisition module is used to obtain the digital invoice issuance request of the business object; A response module, used for responding to the digital invoice issuance request and obtaining the invoice plane code; A page acquisition module, used to acquire an invoice scanning code page according to the invoice plane code; A scanning module, used to scan the invoice code scanning page to obtain the business authentication page of the business object; A permission acquisition module, used to obtain the business permission of the business object on the business authentication page; A generation module is used to generate a digital invoice for the business object according to the business authority.
9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.