Invoice application method and device, intelligent equipment and storage medium
By obtaining user ID and portraits, and calling the initial invoice template to generate a target invoice page, it solves the problem that traditional invoice application methods cannot meet the needs of large-scale users, and achieves rapid and effective invoice application and user experience improvement.
Patent Information
- Application Number
- CN202311340098.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-16
- Publication Date
- 2025-04-18
AI Technical Summary
The traditional invoice application method cannot meet the invoice billing needs of the huge user group, resulting in the extended invoice issuance time and it is easy to cause the invoice to be invalid due to error information.
By obtaining the user's user ID, obtaining the user's user portrait and invoice information, calling the initial invoice template, generating a target invoice page based on the user information, and submitting an invoice issuance application.
It has achieved convenient user application for invoices, improved the speed and effectiveness of invoice applications, and enhanced the user experience.
Smart Images
Figure CN119850280A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information processing technology, and in particular to an invoice application method, apparatus, intelligent device and storage medium. Background Art
[0002] An invoice refers to a business voucher issued and collected by all units and individuals when buying and selling goods, providing or receiving services, and engaging in other business activities. It is the original basis for accounting and an important basis for law enforcement inspections by auditing and tax authorities.
[0003] In recent years, with the rise of shopping platforms and the rapid development of live streaming, the logistics industry has also developed rapidly, which is both an opportunity and a challenge for the logistics industry. Users' demand for invoicing is also increasing. Issuing invoices requires users to fill in relevant information about the invoice. If users cannot quickly provide the invoice information, it will increase the time for invoice issuance. Accidentally using wrong invoice information to issue an invoice will cause the invoice to be invalid and need to be reissued.
[0004] The traditional invoice application method can no longer meet the invoicing needs of a large user group. How to facilitate users to apply for invoices conveniently, improve the speed and effectiveness of invoice application, and enhance user experience are issues that need to be considered at present. Summary of the invention
[0005] The embodiments of the present application provide an invoice application method, apparatus, smart device and storage medium, which can facilitate users to apply for invoices conveniently, improve the speed and effectiveness of invoice application, and enhance user experience.
[0006] In a first aspect, an embodiment of the present application provides an invoice application method, including: obtaining an invoice issuance request, the invoice issuance request carrying a user identifier of a user; based on the invoice issuance request, obtaining a user portrait corresponding to the user identifier, and the user's invoicing information; calling an initial invoicing template corresponding to the user portrait; generating a target invoicing page based on the user's invoicing information and the initial invoicing template; and submitting an invoice issuance application based on the target invoicing page.
[0007] In a possible implementation manner of the first aspect, obtaining the invoice issuance request includes: obtaining an invoice application mode preset by a user; and obtaining the invoice issuance request according to the invoice application mode preset by the user.
[0008] In a possible implementation of the first aspect, the invoice application mode includes automatic application and non-automatic application, and an invoice issuance request is obtained according to the invoice application mode preset by the user, including: if the invoice application mode preset by the user is non-automatic application, triggering the generation of an invoice issuance request according to the invoice application instruction input by the user; if the invoice application mode preset by the user is automatic application, obtaining the automatic application cycle preset by the user; based on the automatic application cycle, generating an invoice issuance request at a regular interval.
[0009] In a possible implementation of the first aspect, calling an initial invoicing template corresponding to a user portrait includes: determining, based on the user portrait, a user-selectable invoice type; and determining an initial invoicing template from preset invoicing templates, wherein the initial invoicing template includes a user-selectable invoice type.
[0010] In a possible implementation of the first aspect, before obtaining a user portrait corresponding to a user identifier based on an invoice issuance request, the method includes: obtaining the user's historical mailing information and the historical value-added services used by the user; generating a user portrait of the user based on the historical mailing information and the historical value-added services; and storing the user portrait of the user on a server.
[0011] In a possible implementation of the first aspect, an embodiment of the present application provides an invoice application method that also includes: regularly accessing a public network server to obtain user-related information; based on the related information, determining whether there is an update field in the user's invoicing information; if there is an update field, generating an invoicing information update instruction, and the invoicing information update instruction is used to prompt the user that there is an update in the invoicing information; when the user's confirmation update instruction is detected, updating the user's invoicing information according to the update field.
[0012] In a second aspect, an embodiment of the present application provides an invoice application device, the device comprising:
[0013] An invoice request acquisition unit, used to acquire an invoice issuance request, the invoice issuance request carries a user ID of the user;
[0014] A portrait and information acquisition unit, used to acquire a user portrait corresponding to a user identifier and the user's invoicing information based on an invoice issuance request;
[0015] An initial template calling unit, used to call the initial invoicing template corresponding to the user portrait;
[0016] A target page generating unit, used to generate a target invoicing page according to the user's invoicing information and the initial invoicing template;
[0017] The invoice application unit is used to submit an invoice application based on the target invoicing page.
[0018] In a third aspect, an embodiment of the present application provides an intelligent device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the invoice application method as described in the first aspect above is implemented.
[0019] In a fourth aspect, an embodiment of the present application provides 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 invoice application method as described in the first aspect above is implemented.
[0020] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a smart device, the smart device executes the invoice application method as described in the first aspect above.
[0021] In the embodiment of the present application, by obtaining an invoice issuance request, the invoice issuance request carries the user's user ID, based on the invoice issuance request, the user portrait corresponding to the user ID and the user's invoicing information are obtained, and then the initial invoicing template corresponding to the user portrait is called, and the initial invoicing template suitable for the user is accurately matched according to the user portrait, which is conducive to improving the effectiveness of the invoicing application, and then the target invoicing page is generated according to the user's invoicing information and the initial invoicing template, and finally the invoice issuance application is submitted according to the target invoicing page. This application can facilitate users to apply for invoices conveniently, improve the speed and effectiveness of invoice applications, and enhance user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present application, 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 of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0023] Figure 1 It is a flowchart of the implementation of the invoice application method provided in the embodiment of the present application;
[0024] Figure 2 It is a specific implementation flow chart of step S101 in the invoice application method provided in the embodiment of the present application;
[0025] Figure 3 It is a specific implementation flow chart of obtaining an invoice issuance request according to the invoice application mode preset by the user in the invoice application method provided in the embodiment of the present application;
[0026] Figure 4It is a specific implementation flow chart of updating the invoicing information of the user in the invoice application method provided in the embodiment of the present application;
[0027] Figure 5 This is a specific implementation flow chart of step S103 in the invoice application method provided in the embodiment of the present application;
[0028] Figure 6 This is a specific implementation flow chart of step S104 of the invoice application method provided in the embodiment of the present application;
[0029] Figure 7 It is a structural block diagram of the invoice application device provided in the embodiment of the present application;
[0030] Figure 8 It is a schematic diagram of a smart device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0031] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0032] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.
[0033] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0034] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.
[0035] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.
[0036] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.
[0037] It should be understood that the invoice application method provided in the embodiment of the present application is applicable to various types of smart devices that need to execute invoice application, which may specifically include mobile phones, tablet computers, wearable devices, laptop computers, and desktop computers. The smart invoice application method provided in the embodiment of the present application can be applied to applications and applets of smart devices, and can also be applied to the WEB end of smart devices. The embodiment of the present application does not impose any restrictions on the specific types of smart devices.
[0038] Figure 1 The implementation process of the invoice application method provided in the embodiment of the present application is shown, and the method flow includes steps S101 to S105. The specific implementation principle of each step is as follows:
[0039] Step S101: obtaining an invoice issuance request, wherein the invoice issuance request carries a user ID of a user.
[0040] In this embodiment, the user needs to log in to the account on the smart device to apply for an invoice. The invoice request carries the user ID of the user's current login account on the smart device. The user ID is unique and can be used to identify the user. For example, the user ID can be an account ID, a mobile phone number, or an ID number.
[0041] As a possible implementation of this application, Figure 2 The specific implementation process of step S101 of the invoice application method provided in the embodiment of the present application is shown. Step S101 specifically includes the following steps:
[0042] S11: Obtain the invoice application mode preset by the user.
[0043] In this embodiment, the invoice application mode includes two modes: automatic application and non-automatic application.
[0044] In a possible implementation, a switching switch for the invoice application mode is provided in the operation interface of the smart invoice application, and the user can switch the invoice application mode by triggering the switching switch.
[0045] Generally, the default mode of the invoice application mode is non-automatic application. In the default mode, when it is detected that the user triggers the switch of the invoice application mode, the invoice application mode is switched from non-automatic application to automatic application.
[0046] S12: Obtain an invoice issuance request according to the invoice application mode preset by the user.
[0047] In this embodiment, the user can preset the invoice application mode, and different invoice application modes have different ways of obtaining invoice requests. By providing two invoice application modes, automatic application and non-automatic application, for users to choose, a variety of services are provided to users. Users can choose different invoice application modes according to their needs, which helps users to apply for invoices conveniently and improves user experience.
[0048] As a possible implementation of the present application, the invoice application mode includes automatic application and non-automatic application, such as Figure 3 As shown, step S12 specifically includes the following steps:
[0049] S121: If the invoice application mode preset by the user is non-automatic application, triggering the generation of an invoice issuance request according to the invoice application instruction input by the user.
[0050] In this embodiment, in the non-automatic application mode, the invoice application instruction input by the user is detected to trigger the invoice application request. For example, the user turns on the invoice application switch by voice or interface touch, generates an invoice application instruction, and thus triggers the invoice application request. In this embodiment, the invoice application request is triggered only after the user confirms that the invoice needs to be applied for, and then actively inputs the invoice application instruction.
[0051] S122: If the invoice application mode preset by the user is automatic application, the automatic application cycle preset by the user is obtained.
[0052] S123: Based on the automatic application cycle, regularly generate an invoice issuance request.
[0053] For long-term and stable users, they will need to apply for invoices regularly. Users can choose the automatic application mode and preset the automatic application cycle, such as automatically applying once a month. The smart device monitors the automatic application cycle through a timer and automatically generates invoice issuance requests regularly. The automatic invoice application mode helps users to actively apply for invoices, avoiding users from failing to apply for invoices in time due to forgetfulness or other reasons, helping users to apply for invoices conveniently, and at the same time, improving the efficiency of invoice application.
[0054] In a possible implementation, after automatically and regularly generating an invoice issuance request, an automatic invoice application reminder is sent to the user, and after receiving the user's confirmation instruction, subsequent steps are continued to automatically apply for an invoice for the user.
[0055] In a possible implementation, if the smart device detects that the user has purchased logistics services but has not applied for an invoice for a long time, that is, if the smart device has not received the user's invoice application instruction within a specified period of time, it can send an invoice application reminder to the user to remind the user that he can apply for an invoice, which is conducive to improving the user experience. For example, when the smart device detects that the user has been actively sending parcels within half a year, but has not detected the user's invoice issuance request, the user is reminded to apply for an invoice through information reminders and other means.
[0056] Step S102: Based on the invoice issuance request, obtain the user portrait corresponding to the user identifier and the invoicing information of the user.
[0057] In this embodiment, after obtaining the invoice issuance request, the smart device obtains the user portrait corresponding to the user identifier and the invoicing information of the user based on the invoice issuance request.
[0058] The invoicing information includes fields required for issuing invoices, such as invoice header, taxpayer identification code, bank account, bank account number, company registration address, etc.
[0059] As a possible implementation of this application, Figure 4 A specific implementation process of updating the user's invoicing information in the invoice application method provided in the embodiment of the present application is shown, and the specific steps include:
[0060] S21: Periodically access the public network server to obtain the user's associated information. The associated information refers to information related to the user's billing information, such as publicly disclosed registration address, registration phone number, etc.
[0061] S22: Based on the association information, determine whether the user's billing information has an updated field. The updated field refers to a field that is different from the billing information saved by the user, such as a registered address update, a registered phone number update, etc.
[0062] S23: If there is an update field, a billing information update instruction is generated, where the billing information update instruction is used to prompt the user that the billing information is updated.
[0063] S24: When the user's confirmation update instruction is detected, the user's billing information is updated according to the update field.
[0064] In this embodiment, when a user applies for an invoice, the user is prompted that there is an update field in the invoicing information, and the user is asked to confirm whether to update the invoicing information. When the user's confirmation update instruction is detected, the corresponding original field in the user's invoicing information is replaced with the update field, and the updated invoicing information is saved.
[0065] When certain fields in the user's invoicing information are updated, the user may not be able to modify and update them in time. If the old invoicing information is used to apply for an invoice, it is very likely that the applied invoice will be invalid. To ensure the validity of the invoice application, in an embodiment of the present application, the public network server is accessed regularly to obtain the user's associated information, and the associated information is compared with the invoicing information saved by the user to determine whether there is an updated field in the invoicing information. If there is an updated field, when the user applies for an invoice, the user is prompted that the original saved invoicing information has been updated to avoid invalidating the invoice applied for by the user.
[0066] In some implementations, when the user's confirmation not to update instruction is detected, the original saved billing information is continued to be used to apply for an invoice for the user. It should be noted that the original saved billing information refers to the billing information most recently saved by the user.
[0067] Step S103: calling the initial invoicing template corresponding to the user portrait.
[0068] The initial invoicing template includes an information box required for applying for an invoice. The information box required for applying for an invoice in the initial invoicing template may be different depending on the user profile.
[0069] As a possible implementation of this application, Figure 5 A specific implementation process of calling the initial invoicing template corresponding to the user portrait in the invoice application method provided in the embodiment of the present application is shown, and step S103 specifically includes the following steps:
[0070] S31: Determine the invoice type that the user can select based on the user portrait.
[0071] In this embodiment, the user's optional invoice type is determined by the user portrait. The invoice type includes paper invoices and electronic invoices, specifically including VAT electronic ordinary invoices, VAT special invoices, all-electric general invoices, and all-electric special invoices.
[0072] S32: Determine an initial invoicing template from preset invoicing templates, wherein the initial invoicing template includes invoice types selectable by the user.
[0073] In the embodiment of the present application, multiple types of invoicing templates are pre-set, and the invoicing templates include information boxes required for applying for invoices. Each invoicing template can be identified by setting a key value Key. Different invoicing templates have different invoice types that users can select. In other words, different invoicing templates have different numbers of information boxes about invoice types.
[0074] This invoicing template can be applied to different clients such as mini-programs, web pages, and applications, and is particularly universal.
[0075] There is a corresponding relationship between the invoicing template and the invoice types and quantities that can be selected by the user. The invoice types that can be selected by users with different user profiles may be different. In this embodiment, the user's profile is used to accurately match the user with the selectable invoice type, avoiding the efficiency of invoice application being affected by the wrong recommendation or missed recommendation of the invoice type.
[0076] As a possible implementation mode of the present application, in order to improve the efficiency of invoicing service matching and save the user's invoicing time, in an embodiment of the present application, the user's historical shipping information and the historical value-added services used by the user are obtained. The historical shipping information includes sender information, recipient information, and consignment information. The historical value-added services include functional services provided by the logistics company. Based on the historical shipping information and the historical value-added services, a user profile of the user is generated. The user profile of the user is stored in a server. The server is a remote server or a cloud server that is connected to the smart device for communication.
[0077] This embodiment generates a user portrait containing rich information based on the user's historical mailing information and the historical value-added services used by the user, which is conducive to accurately matching services for users, thereby improving the speed and effectiveness of service matching and enhancing user experience.
[0078] In this embodiment, the user portrait is composed of multiple tags, including user tags, flow tags, consignment tags, and service tags.
[0079] In some implementations, the user tag of the user is determined based on the sender information; the flow tag of the user is determined based on the recipient information; the consignment tag of the user is determined based on the consignment information; and the service tag of the user is determined based on the historical value-added services. The user profile of the user is determined based on the user tag, flow tag, consignment tag, and service tag.
[0080] Step S104: Generate a target invoicing page according to the user's invoicing information and the initial invoicing template.
[0081] As a possible implementation of the present application, the initial invoicing template includes the invoice type selectable by the user, Figure 6 A specific implementation process of step S104 in the invoice application method provided in the embodiment of the present application is shown, and is described in detail as follows:
[0082] S41: Obtain the invoice type selected by the user.
[0083] In this embodiment, based on the above initial invoicing template, the invoice type selected by the user is obtained.
[0084] S42: Based on the invoice type selected by the user, update the target information box in the initial invoicing template.
[0085] In this embodiment, the target information box in the initial invoicing template is different for different invoice types. For example, the target information box in the initial invoicing template is the recipient information box. For paper invoices, the target information box specifically includes information boxes for entering the recipient's name, detailed address of the recipient, etc. For electronic invoices, the target information box specifically includes an information box for entering the recipient's email address.
[0086] S43: According to the target information box, target invoicing information is determined from the invoicing information of the user. The target invoicing information is determined according to the requirements of the invoice type. For example, for a paper invoice, the target invoicing information includes the name of the recipient and the detailed address of the recipient; while for an electronic invoice, the target invoicing information includes the recipient's email address.
[0087] S44: Fill the target invoicing information into the target information box to generate a target invoicing page.
[0088] In this embodiment, the initial invoicing template is encapsulated into a json data format suitable for page rendering, and then the initial invoicing template in the json data format is converted into a template AST (Abstract Syntax Tree), combined with the target invoicing information, the AST tree related to the invoicing page is output, and then the invoicing page code of different ends is generated through the AST parser to obtain the target invoicing page.
[0089] In the embodiment of the present application, the AST tree related to the invoicing page is reusable, and the invoicing page code suitable for different terminals can be generated by the parser, so that cross-platform page rendering can be realized.
[0090] Step S105: Submit an invoice issuance application according to the target invoicing page.
[0091] In this embodiment, the target invoicing page is displayed on the smart device, and after obtaining the user's confirmation application instruction, an invoice issuance application is submitted. The invoice issuance application is used to issue an invoice for the user according to the invoicing information in the target invoicing page.
[0092] In the embodiment of the present application, by obtaining an invoice issuance request, the invoice issuance request carries the user's user ID, based on the invoice issuance request, the user portrait corresponding to the user ID and the user's invoicing information are obtained, and then the initial invoicing template corresponding to the user portrait is called, and the initial invoicing template suitable for the user is accurately matched according to the user portrait, which is conducive to improving the effectiveness of the invoicing application, and then the target invoicing page is generated according to the user's invoicing information and the initial invoicing template, and finally the invoice issuance application is submitted according to the target invoicing page. This application can facilitate users to apply for invoices conveniently, improve the speed and effectiveness of invoice applications, and enhance user experience.
[0093] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0094] Corresponding to the invoice application method described in the above embodiment, Figure 7 A structural block diagram of an invoice application device provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.
[0095] Reference Figure 7 The invoice application device includes: an invoice request acquisition unit 71, a portrait and information acquisition unit 72, an initial template calling unit 73, a target page generation unit 74, and an invoice application unit 75, wherein:
[0096] An invoice request acquisition unit 71 is used to acquire an invoice issuance request, wherein the invoice issuance request carries a user ID of a user;
[0097] A portrait and information acquisition unit 72, configured to acquire a user portrait corresponding to the user identifier and the user's invoicing information based on the invoice issuance request;
[0098] An initial template calling unit 73, used to call the initial invoicing template corresponding to the user portrait;
[0099] A target page generating unit 74, configured to generate a target invoicing page according to the invoicing information of the user and the initial invoicing template;
[0100] The invoice application unit 75 is used to submit an invoice application according to the target invoicing page.
[0101] As a possible implementation of the present application, the invoicing request obtaining unit 71 includes:
[0102] A mode acquisition module is used to obtain the invoice application mode preset by the user;
[0103] The request acquisition module is used to acquire an invoice issuance request according to the invoice application mode preset by the user.
[0104] As a possible implementation of the present application, the invoice application mode includes automatic application and non-automatic application, and the request acquisition module includes:
[0105] A first request acquisition submodule, configured to trigger the generation of an invoice issuance request according to the invoice application instruction input by the user if the invoice application mode preset by the user is non-automatic application;
[0106] The second request acquisition submodule is used to obtain the automatic application cycle preset by the user if the invoice application mode preset by the user is automatic application; and to generate an invoice issuance request regularly based on the automatic application cycle.
[0107] As a possible implementation of the present application, the initial template calling unit 73 includes:
[0108] An optional type determination module, used to determine the invoice type that the user can select based on the user portrait;
[0109] The initial template determination module is used to determine an initial invoicing template from preset invoicing templates, wherein the initial invoicing template includes an invoice type selectable by the user.
[0110] As a possible implementation of the present application, the initial invoicing template includes the invoice type selectable by the user, and the target page generating unit 74 includes:
[0111] A type determination module, used for obtaining the invoice type selected by the user;
[0112] An information box updating module, used for updating a target information box in the initial invoicing template based on the invoice type selected by the user;
[0113] A target information determination module, used to determine target invoicing information from the invoicing information of the user according to the target information box;
[0114] The target page generating module is used to fill the target invoicing information into the target information box to generate a target invoicing page.
[0115] As a possible implementation of the present application, the invoice application device further includes:
[0116] A historical information acquisition unit, used to acquire the historical mailing information of the user and the historical value-added services used by the user;
[0117] A user portrait generating unit, configured to generate a user portrait of the user according to the historical mailing information and the historical value-added services;
[0118] The portrait storage unit is used to store the user portrait of the user in the server.
[0119] As a possible implementation of the present application, the invoice application device further includes:
[0120] A correlation information acquisition unit, used to periodically access a public network server to acquire the correlation information of the user;
[0121] An update determination unit, configured to determine whether an update field exists in the billing information of the user based on the associated information;
[0122] An update prompting unit, used for generating a billing information update instruction if there is an update field, wherein the billing information update instruction is used for prompting the user that the billing information is updated;
[0123] The billing information updating unit is used to update the billing information of the user according to the update field when a confirmation update instruction of the user is detected.
[0124] In the embodiment of the present application, by obtaining an invoice issuance request, the invoice issuance request carries the user's user ID, based on the invoice issuance request, the user portrait corresponding to the user ID and the user's invoicing information are obtained, and then the initial invoicing template corresponding to the user portrait is called, and the initial invoicing template suitable for the user is accurately matched according to the user portrait, which is conducive to improving the effectiveness of the invoicing application, and then the target invoicing page is generated according to the user's invoicing information and the initial invoicing template, and finally the invoice issuance application is submitted according to the target invoicing page. This application can facilitate users to apply for invoices conveniently, improve the speed and effectiveness of invoice applications, and enhance user experience.
[0125] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.
[0126] The present application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, Figures 1 to 6 The steps of any invoice application method are shown.
[0127] The embodiment of the present application also provides an intelligent device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, Figures 1 to 6 The steps of any invoice application method are shown.
[0128] The present application also provides a computer program product, which, when executed on a server, enables the server to execute the following Figures 1 to 6 The steps of any invoice application method are shown.
[0129] Figure 8 Schematic diagram of a smart device provided by an embodiment of the present application. Figure 8 As shown, the smart device 8 of this embodiment includes: a processor 80, a memory 81, and a computer program 82 stored in the memory 81 and executable on the processor 80. When the processor 80 executes the computer program 82, the steps in the above-mentioned invoice application method embodiments are implemented, for example Figure 1 Alternatively, when the processor 80 executes the computer program 82, the functions of each module / unit in the above-mentioned device embodiments are realized, for example Figure 7 The functions of the units 71 to 75 are shown.
[0130] Exemplarily, the computer program 82 may be divided into one or more modules / units, which are stored in the memory 81 and executed by the processor 80 to complete the present application. The one or more modules / units may be a series of computer-readable instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 82 in the smart device 8.
[0131] The smart device 8 may include, but is not limited to, a processor 80 and a memory 81. Those skilled in the art will appreciate that Figure 8 It is only an example of the smart device 8 and does not constitute a limitation of the smart device 8. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the smart device 8 may also include input and output devices, network access devices, buses, etc.
[0132] The processor 80 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0133] The memory 81 may be an internal storage unit of the smart device 8, such as a hard disk or memory of the smart device 8. The memory 81 may also be an external storage device of the smart device 8, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the smart device 8. Further, the memory 81 may also include both an internal storage unit and an external storage device of the smart device 8. The memory 81 is used to store the computer program and other programs and data required by the smart device. The memory 81 may also be used to temporarily store data that has been output or is to be output.
[0134] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.
[0135] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.
[0136] 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 present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.
[0137] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0138] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. An invoice application method, characterized in that: The method comprises: Obtain an invoice issuance request, where the invoice issuance request carries a user ID of the user; Based on the invoice issuance request, obtaining a user portrait corresponding to the user identifier and the invoicing information of the user; Calling the initial invoicing template corresponding to the user portrait; Generate a target invoicing page according to the invoicing information of the user and the initial invoicing template; Submit an invoice application according to the target invoicing page.
2. The invoice application method according to claim 1, characterized in that: The invoice issuance request includes: Get the invoice application mode preset by the user; According to the invoice application mode preset by the user, an invoice issuance request is obtained.
3. The invoice application method according to claim 2, characterized in that: The invoice application mode includes automatic application and non-automatic application. The obtaining of the invoice issuance request according to the invoice application mode preset by the user includes: If the invoice application mode preset by the user is non-automatic application, triggering the generation of an invoice issuance request according to the invoice application instruction input by the user; If the invoice application mode preset by the user is automatic application, obtaining the automatic application cycle preset by the user; Based on the automatic application cycle, an invoice issuance request is generated regularly.
4. The invoice application method according to claim 1, characterized in that: The calling of the initial invoicing template corresponding to the user portrait includes: Determining the invoice type that the user can select based on the user portrait; An initial invoicing template is determined from preset invoicing templates, wherein the initial invoicing template includes an invoice type selectable by the user.
5. The invoice application method according to claim 1, characterized in that: The initial invoicing template includes an invoice type selectable by the user, and generating a target invoicing page according to the invoicing information of the user and the initial invoicing template includes: Get the invoice type selected by the user; Based on the invoice type selected by the user, updating the target information box in the initial invoicing template; According to the target information box, determining target billing information from the billing information of the user; Fill the target invoicing information into the target information box to generate a target invoicing page.
6. The invoice application method according to any one of claims 1 to 5, characterized in that: Before obtaining the user portrait corresponding to the user identifier based on the invoice issuance request, the method includes: Obtain the historical mailing information of the user and the historical value-added services used by the user; Generate a user profile of the user based on the historical mailing information and the historical value-added services; The user profile of the user is stored in the server.
7. The invoice application method according to any one of claims 1 to 5, characterized in that: The method further comprises: Regularly access the public network server to obtain the user's related information; Based on the associated information, determining whether there is an update field in the billing information of the user; If there is an update field, a billing information update instruction is generated, and the billing information update instruction is used to prompt the user that the billing information has been updated; When the user's confirmation update instruction is detected, the user's billing information is updated according to the update field.
8. An invoice application device, characterized in that: The device comprises: An invoice request acquisition unit, used to acquire an invoice issuance request, wherein the invoice issuance request carries a user ID of a user; A portrait and information acquisition unit, configured to acquire a user portrait corresponding to the user identifier and the user's invoicing information based on the invoice issuance request; An initial template calling unit, used to call the initial invoicing template corresponding to the user portrait; A target page generating unit, configured to generate a target invoicing page according to the invoicing information of the user and the initial invoicing template; The invoice application unit is used to submit an invoice application according to the target invoicing page.
9. An intelligent device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the invoice application method according to any one of claims 1 to 7 is implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the invoice application method according to any one of claims 1 to 7 is implemented.