A method, apparatus, electronic device and readable storage medium for providing an invoice
By setting a target invoice provision strategy before charging stations go online, the problem of inaccurate invoice issuance at charging stations has been solved, ensuring the accuracy and flexibility of invoicing and meeting the invoicing needs of different business types.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- ZHEJIANG ANJI INTELLIGENT ELECTRONICS HLDG CO LTD
- Filing Date
- 2022-12-12
- Publication Date
- 2026-06-09
AI Technical Summary
In the existing technology, the invoice issuance method of charging stations is inaccurate, especially when the operating company does not have the ability to issue invoices, which makes it impossible to provide invoices to enterprises, and untimely configuration will also lead to inaccurate invoicing methods.
Before a charging station goes online, the invoice provision strategy of its operating company is determined, a target invoice provision strategy is set, and invoices are issued according to the strategy after going online. This includes obtaining invoice requests from users, responding to and issuing invoices according to the strategy, supporting changes to the invoice provision strategy and confirmation by financial personnel.
It enables timely configuration of invoice provision strategies before charging stations go online, ensuring the accuracy and flexibility of invoicing and meeting the invoicing needs of different business types.
Smart Images
Figure CN116228336B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a method for providing invoices, an apparatus for providing invoices, an electronic device, and a readable storage medium. Background Technology
[0002] Currently, the method of issuing invoices for charging scenarios involving vehicles and other means of transportation is determined by the business model of the operating company that owns the charging station. For example, if the operating company does not have the ability to issue invoices, such as if the operating company is a small-scale taxpayer (e.g., a sole proprietorship), then the operating company cannot issue invoices to businesses, and therefore the charging stations owned by that operating company cannot be opened to those businesses.
[0003] In related technologies, whether the operating company can issue invoices is configured after the charging station goes online. If the configuration is not timely, the invoicing method provided to users who request invoices will be inaccurate. Summary of the Invention
[0004] In view of this, this application provides a method for providing invoices, an apparatus for providing invoices, an electronic device, and a readable storage medium, which solves the problem of inaccurate invoicing in the related art.
[0005] In a first aspect, embodiments of this application provide a method for providing invoices, applied to a charging application. The method includes: determining a charging station to be launched, and obtaining the invoice provision strategy of a first operating company to which the charging station to be launched belongs; setting a first target invoice provision strategy for the charging station to be launched according to the invoice provision strategy of the first operating company, and launching the charging station to be launched; obtaining an invoice request from a requesting user, and in response to the invoice request, issuing an invoice according to the first target invoice provision strategy.
[0006] The method described in the embodiments of this application may also have the following additional technical features:
[0007] Optionally, in the above technical solution, the method further includes: obtaining a change request from the second operating company for its invoice provision strategy; determining the second target invoice provision strategy carried in the change request; and changing the second operating company's invoice provision strategy to the second target invoice provision strategy.
[0008] Optionally, in any of the above technical solutions, before setting the first target invoice provision strategy for the charging station to be launched, or changing the invoice provision strategy of the second operating company to the second target invoice provision strategy, the method further includes: sending a first confirmation request to the terminal device of the finance personnel, the first confirmation request being used to instruct the finance personnel to confirm the first target invoicing or the second target invoice provision strategy.
[0009] In any of the above technical solutions, optionally, setting a first target invoice provision strategy for the charging station to be launched, based on the invoice provision strategy of the first operating company, includes: if the first operating company includes one invoice provision strategy, then setting the invoice provision strategy as the first target invoice provision strategy for the charging station to be launched; if the first operating company includes multiple invoice provision strategies, then sending a second confirmation request to the terminal equipment of the first operating company, the second confirmation request being used to instruct the first operating company to select one invoice provision strategy from the multiple invoice provision strategies; obtaining confirmation information fed back by the terminal equipment of the first operating company, and setting the invoice provision strategy indicated in the confirmation information as the first target invoice provision strategy for the charging station to be launched.
[0010] In any of the above technical solutions, optionally, the invoice provision strategy of the first operating company includes at least one of the following: the company owning the charging application issues all invoices, the company owning the charging application does not issue any invoices, or the company owning the charging application only issues invoices to enterprises; the business type of the company owning the charging application includes at least one of the following: enterprise version, self-operated version, and downstream channel version.
[0011] In any of the above technical solutions, optionally, if the business type corresponding to the requesting user is the enterprise version, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: if the first target invoice provision strategy is that the company owning the charging application issues all invoices, then the company owning the application issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, then no invoice is issued for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, then the company owning the application issues an invoice for the requesting user.
[0012] In any of the above technical solutions, optionally, if the business type corresponding to the requesting user is a self-operated terminal, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: if the first target invoice provision strategy is that the company owning the charging application issues all invoices, then the company owning the application issues the invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, then the first operating company issues the invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, then the first operating company issues the invoice for the requesting user.
[0013] In any of the above technical solutions, optionally, if the business type corresponding to the requesting user is the downstream channel version, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: in response to the invoice request, obtaining the invoice type of the downstream channel version, the invoice type of the downstream channel version includes issuing an invoice and not issuing an invoice; issuing an invoice according to the invoice type of the downstream channel version and the first target invoice provision strategy.
[0014] In any of the above technical solutions, optionally, invoicing is performed based on the invoice type of the downstream channel version and the first target invoice provision strategy, including: if the first target invoice provision strategy is that the company owning the charging application issues all invoices, and the invoice type of the downstream channel version is either issuing an invoice or not issuing an invoice, then the company owning the application issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, and the invoice type of the downstream channel version is issuing an invoice, then no invoice is issued for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, and the invoice type of the downstream channel version is not issuing an invoice, then the first operating company issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the invoice type of the downstream channel version is issuing an invoice, then the company owning the application issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the invoice type of the downstream channel version is not issuing an invoice, then the first operating company issues an invoice for the requesting user.
[0015] Secondly, embodiments of this application provide an invoice-providing device applied to a charging application. The device includes: an acquisition module, configured to determine a charging station to be launched and acquire the invoice provision strategy of a first operating company to which the charging station to be launched belongs; a processing module, configured to set a first target invoice provision strategy for the charging station to be launched based on the invoice provision strategy of the first operating company, and launch the charging station to be launched; and an invoicing module, configured to acquire an invoice request from a requesting user and, in response to the invoice request, issue an invoice according to the first target invoice provision strategy.
[0016] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions implementing the steps of the method as described in the first aspect when executed by the processor.
[0017] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first aspect.
[0018] Fifthly, embodiments of this application provide a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.
[0019] In a sixth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method as described in the first aspect.
[0020] In this embodiment, charging stations to be launched are periodically identified. After a charging station is identified, the invoice provision strategy of the first operating company to which the charging station belongs is obtained. Further, based on the first operating company's invoice provision strategy, a first target invoice provision strategy corresponding to the charging station to be launched is determined, thus setting the invoice provision strategy for the charging station to be launched and launching the charging station after setting the invoice provision strategy. After the charging station is launched, it will provide charging functionality. After charging, if a user requests an invoice, an invoice will be issued to the requesting user according to the charging station's first target invoice provision strategy. The requesting user can be an individual user, a corporate user, or a user of a downstream channel company, etc.
[0021] In this embodiment, the invoice issuance logic is optimized. Specifically, the invoice provision strategy is determined before the charging station goes online, so that the invoice provision strategy can be configured for the charging station in a timely manner to ensure the accuracy of invoicing.
[0022] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description
[0023] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:
[0024] Figure 1 One of the flowcharts illustrating a method for providing an invoice according to an embodiment of this application is shown;
[0025] Figure 2 A second schematic flowchart illustrating a method for providing an invoice according to an embodiment of this application is shown;
[0026] Figure 3 The third schematic flowchart illustrates a method for providing invoices according to an embodiment of this application;
[0027] Figure 4 The fourth schematic flowchart illustrates a method for providing an invoice according to an embodiment of this application;
[0028] Figure 5 A structural block diagram of an apparatus for providing invoices according to an embodiment of this application is shown;
[0029] Figure 6 A structural block diagram of an electronic device according to an embodiment of this application is shown. Detailed Implementation
[0030] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0031] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0032] The following description, in conjunction with the accompanying drawings, details the method, apparatus, electronic device, and readable storage medium for providing invoices provided in this application, through specific embodiments and application scenarios.
[0033] This application provides a method for providing invoices, which is applied to a charging application. The charging application can be an APP or a mini-program. The charging application is a third-party charging network used to connect charging operation companies of different brands, accelerate the interconnection of charging piles, and enable car owners to realize functions such as online navigation, finding charging piles, charging, and issuing invoices after charging through the charging application.
[0034] The charging applications are developed by third-party charging companies, and their business types include enterprise versions, self-operated versions, and downstream channel versions. The self-operated version refers to the third-party charging company directly providing the above functions to individual users, belonging to the B2C (Business to Customer) model. The enterprise version and downstream channel version belong to the B2B2C (Business to Business to Customer) model, meaning the third-party charging company provides the above functions to enterprises. The difference between the enterprise version and the downstream channel version is that the enterprise users are fleet operators who use the SaaS (Software-as-a-Service) provided by the third-party charging company for enterprise management, driver management, charging management, account management, etc. The downstream channel users are channel companies who do not use the SaaS provided by the third-party charging company but have their own APP or system. It is an open platform of the third-party charging company's charging application. The third-party charging company signs contracts with channel companies to open up the above functions, enabling channel companies to perform these functions on their own APP or system.
[0035] like Figure 1 As shown, the method for providing an invoice includes:
[0036] Step 101: Identify the charging stations to be launched and obtain the invoice provision strategy from the first operating company to which the charging stations belong;
[0037] Step 102: Based on the invoice provision strategy of the first operating company, set the first target invoice provision strategy for the charging stations to be launched, and launch the charging stations to be launched.
[0038] Step 103: Obtain the invoice request from the requesting user, and in response to the invoice request, issue an invoice according to the first target invoice provision strategy.
[0039] To address the issue of inaccurate invoices, this application optimizes the invoice issuance logic by determining the invoice provision strategy before a charging station goes online. Specifically, charging stations to be launched are identified periodically, and after each station is identified, the invoice provision strategy of the first operating company to which that station belongs is obtained. The relationship between the charging station and the operating company is that the charging station's orders are settled by its operating company.
[0040] It should be noted that the invoice provision strategy of the primary operating company to which the charging stations to be launched belong is determined when the primary operating company signs a cooperation agreement with the third-party charging company (i.e., the company that owns the charging application). The invoice provision strategy includes at least one of the following: the third-party charging company issues all invoices, the third-party charging company does not issue any invoices, and the third-party charging company only issues invoices to enterprises. Among them, the third-party charging company issues all invoices, which means that the third-party charging company issues invoices regardless of the type of service used by the requesting user. The third-party charging company does not issue any invoices, which means that the third-party charging company does not issue invoices regardless of the type of service used by the requesting user. The third-party charging company only issues invoices to enterprises, which means that the third-party charging company only issues invoices to fleet companies or channel companies, and does not issue invoices to individual users.
[0041] Furthermore, based on the invoice provision strategy of the first operating company, the first target invoice provision strategy corresponding to the charging station to be launched is determined, thereby realizing the setting of the invoice provision strategy for the charging station to be launched, and launching the charging station after setting the invoice provision strategy.
[0042] It's worth noting that after determining the initial invoice provision strategy for the charging stations to be launched, it's also possible to determine whether the charging stations should provide invoices for certain business types based on this strategy and the business types of the third-party charging companies. Specifically, if the initial invoice provision strategy determines that invoicing cannot be provided for certain business types, then the charging stations will not provide invoices for those business types, effectively blocking them. This method allows for the determination of whether a charging station should provide invoices, avoiding the problem of not being able to meet the invoicing needs of requesting users.
[0043] Once the charging station is online, it will provide charging functionality. After charging, if the requesting user needs an invoice, the invoice will be issued according to the charging station's primary invoicing policy. The requesting user can be an individual user, a corporate user, or a user of a downstream channel company, etc.
[0044] In this embodiment, the invoice issuance logic is optimized. Specifically, the invoice provision strategy is determined before the charging station goes online, so that the invoice provision strategy can be configured for the charging station in a timely manner to ensure the accuracy of invoicing.
[0045] In one embodiment of this application, the method further includes: obtaining a change request from a second operating company for an invoice provision strategy; determining a second target invoice provision strategy carried in the change request; and changing the second operating company's invoice provision strategy to the second target invoice provision strategy.
[0046] In this embodiment, when the second operating company requests a change in its invoice provision strategy, the change in its invoice provision strategy is implemented in accordance with the second operating company's request.
[0047] Furthermore, after determining the second target invoice provision strategy in the change request, the external playback logic of the charging station will also be determined based on the second target invoice provision strategy.
[0048] The above methods provide the function of changing the invoice provision strategy of the operating company, thus meeting the needs of the operating company to change its invoice provision strategy.
[0049] In one embodiment of this application, before setting the first target invoice provision strategy for the charging station to be launched, or changing the invoice provision strategy of the second operating company to the second target invoice provision strategy, the method further includes: sending a first confirmation request to the terminal device of the finance personnel, the first confirmation request being used to instruct the finance personnel to confirm the first target invoicing or the second target invoice provision strategy.
[0050] In this embodiment, whether it is binding the invoice provision strategy before the charging station goes online, or the operating company applies to change the invoice provision strategy, it needs to be sent to the financial system (that is, the terminal device of the financial personnel) for review by the financial personnel before going online or making changes.
[0051] In addition, the financial orders pushed by the financial system need to be updated with fields for business type and invoice type. The invoice type is the type of invoice determined according to the final first target invoice provision strategy, including invoices issued by the company that owns the charging application or by the first operating company.
[0052] In this embodiment of the application, the accuracy of the invoice provision strategy can be ensured through the review by financial personnel, thereby ensuring the accuracy of subsequent invoicing.
[0053] In one embodiment of this application, the first operating company includes one or more invoice provision strategies. If the first operating company includes one invoice provision strategy, the invoice provision strategy is set as the first target invoice provision strategy for the charging station to be launched. If the first operating company includes multiple invoice provision strategies, a second confirmation request is sent to the terminal device of the first operating company. The second confirmation request is used to instruct the first operating company to select one invoice provision strategy from the multiple invoice provision strategies. Confirmation information fed back by the terminal device of the first operating company is obtained, and the invoice provision strategy indicated in the confirmation information is set as the first target invoice provision strategy for the charging station to be launched.
[0054] In this embodiment, charging stations of operating companies that have been connected with third-party charging companies are periodically retrieved. If a new station is launched, its invoice provision strategy must be confirmed before the new station goes live. The invoice provision strategy of the new station is the invoice provision strategy stipulated in the contract data between its operating company and the third-party charging company, and the invoice provision strategy stipulated in the contract data can be one or more.
[0055] If the contract data includes only one invoice provision strategy, then that invoice provision strategy will be directly bound before the new site goes live. If the contract data includes multiple invoice provision strategies, then the business or operations personnel of the operating company need to confirm one invoice provision strategy among the multiple invoice provision strategies, and then bind the invoice provision strategy confirmed by the business or operations personnel before the new site goes live.
[0056] By using the above methods, an invoice provision strategy can be selected to achieve binding before the site goes online, so as to ensure the accuracy of invoicing after the site goes online.
[0057] In some embodiments, sites to be launched can be bound in batches. For example, if there are 10 sites to be launched and they all need to have the same invoice provision strategy, then these 10 sites can be bound to the same invoice provision strategy in batches. It should be noted that the multiple sites to be launched in batches can belong to the same operating company or different operating companies.
[0058] Additionally, in some embodiments, the sites to be launched by an operating company can be batch-bound according to the operating company dimension. For example, if operating company A includes 5 sites to be launched and operating company A has only one invoice provision strategy, then these 5 sites to be launched will be batch-bound with the invoice provision strategy; if operating company A includes 5 sites to be launched and operating company A includes multiple invoice provision strategies, then the invoice provision strategy confirmed by the business personnel or operations personnel will be bound to the 5 sites to be launched by operating company A.
[0059] It should be noted that the invoice provision strategy is tied to the charging station, not the operating company. Different charging stations under the same operating company may have different invoice provision strategies.
[0060] In this embodiment of the application, the binding efficiency is improved through the batch binding of the above-mentioned different dimensions.
[0061] In one embodiment of this application, when issuing an invoice, an invoice is issued to the requesting user based on a strategy provided by a bound first target invoice and in combination with different business types of the charging application.
[0062] Specifically, such as Figure 2As shown, if the business type corresponding to the requesting user is the enterprise version, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: if the first target invoice provision strategy is that the company owning the charging application issues all invoices, then the company owning the charging application issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, then no invoice is issued for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, then the company owning the charging application issues an invoice for the requesting user.
[0063] In this embodiment, when the requesting user is a company, and the invoice provision strategy of the charging station is that the company owning the charging application issues all invoices, the operating company of the charging station issues an invoice to the company owning the charging application, and the company owning the charging application then issues an invoice to the company.
[0064] When the invoicing policy of charging stations stipulates that the company owning the charging application will not issue invoices, invoices will not be issued to enterprises. Furthermore, under this policy, charging stations will block the enterprise version of their invoices, meaning they will not release the enterprise version to external parties. The reason the charging application's company owns will not issue invoices to enterprises is that the charging station's operating company cannot issue invoices to the charging application's company owning company. Therefore, this policy means that under this policy, charging stations will not release invoices to enterprises.
[0065] When the invoicing strategy for charging stations is such that the company owning the charging application only issues invoices to businesses, the charging station operating company issues the invoice to the company owning the charging application, and then the company owning the charging application issues the invoice to the businesses.
[0066] like Figure 3 As shown, if the business type corresponding to the requesting user is a self-operated terminal, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: if the first target invoice provision strategy is that the company owning the charging application issues all invoices, then the company owning the charging application issues the invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, then the first operating company issues the invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, then the first operating company issues the invoice for the requesting user.
[0067] In this embodiment, the requesting user is an individual user. When the invoice provision strategy of the charging station is that the company owning the charging application issues all invoices, the operating company of the charging station issues an invoice to the company owning the charging application, and the company owning the charging application then issues an invoice to the individual user.
[0068] When the invoicing policy for charging stations stipulates that the company owning the charging application does not issue invoices, the operating company issues invoices to individual users.
[0069] The invoicing policy at charging stations stipulates that when the company owning the charging application only issues invoices to businesses, the operating company issues invoices to individual users.
[0070] In one embodiment of this application, if the business type corresponding to the requesting user is the downstream channel version, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: in response to the invoice request, obtaining the invoice type of the downstream channel version, the invoice type of the downstream channel version includes issuing an invoice and not issuing an invoice; issuing an invoice according to the invoice type of the downstream channel version and the first target invoice provision strategy.
[0071] In this embodiment, when the company that owns the charging application and the downstream channel enterprise sign a contract, it is stipulated whether the channel enterprise will issue an invoice to the user. Then, the invoice type is set in the channel information to determine the invoicing logic and the charging station external playback logic.
[0072] It should be noted that the invoice type is planned by the channel company and then called by the company that owns the charging application.
[0073] like Figure 4 As shown, if the business type corresponding to the requesting user is the downstream channel version, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: if the first target invoice provision strategy is that the charging application's parent company issues all invoices, and the downstream channel version's invoice type is either invoice or no invoice, then the charging application's parent company issues an invoice for the requesting user; if the first target invoice provision strategy is that the charging application's parent company does not issue any invoices, and the downstream channel version's invoice type is invoice, then no invoice is issued for the requesting user; if the first target invoice provision strategy is that the charging application's parent company does not issue any invoices, and the downstream channel version's invoice type is no invoice, then the first operating company issues an invoice for the requesting user; if the first target invoice provision strategy is that the charging application's parent company only issues invoices to enterprises, and the downstream channel version's invoice type is invoice, then the charging application's parent company issues an invoice for the requesting user; if the first target invoice provision strategy is that the charging application's parent company only issues invoices to enterprises, and the downstream channel version's invoice type is no invoice, then the first operating company issues an invoice for the requesting user.
[0074] In this embodiment, if the requesting user is a downstream channel enterprise, the invoice type of the downstream channel enterprise is determined. When the invoice provision strategy of the charging station is that the company owning the charging application issues all invoices, regardless of whether the downstream channel enterprise requests an invoice or not, the company owning the charging application will issue an invoice for the requesting user. Specifically, if the downstream channel enterprise requests an invoice, the charging station operating company issues an invoice to the company owning the charging application, which then issues an invoice to the downstream channel enterprise, which in turn issues an invoice to its individual user; if the downstream channel enterprise requests an invoice but not, the charging station operating company issues an invoice to the company owning the charging application, which then issues an invoice to the individual user of the downstream channel enterprise.
[0075] When the charging station's invoicing policy dictates that the company owning the charging app does not issue invoices, if a downstream channel company's invoice type is "invoice to user," then the charging station will not issue invoices to the individual users of that downstream channel company, and the charging station will block such invoices from being released to other channels. The charging app's owning company does not issue invoices to downstream channel companies because the operating company cannot issue invoices to the charging app's owning company. Therefore, the charging app's owning company cannot issue invoices to downstream channel companies, meaning that under this policy, the charging station will not release invoices to downstream channel companies. If the downstream channel company's invoice type is "not invoice to user," then the charging station's operating company will issue invoices to the individual users of that downstream channel company.
[0076] When the invoicing strategy at charging stations is that the company owning the charging application only issues invoices to businesses, if the downstream channel companies issue invoices to users, then the charging station operating company issues invoices to the company owning the charging application, which in turn issues invoices to the downstream channel companies, who then issue invoices to their individual users. If the downstream channel companies do not issue invoices to users, then the charging station operating company issues invoices to the individual users of the downstream channel companies.
[0077] This application embodiment can provide invoice issuance strategies for different business terminals, improve invoice issuance flexibility, and meet invoice issuance requirements.
[0078] As a specific implementation of the above-described method for providing invoices, this application provides an apparatus for providing invoices. For example... Figure 5 As shown, the invoice-providing device 500 includes: an acquisition module 501, a processing module 502, and an invoice-issuing module 503.
[0079] The acquisition module 501 is used to determine the charging stations to be launched and to acquire the invoice provision strategy of the first operating company to which the charging stations to be launched belong; the processing module 502 is used to set the first target invoice provision strategy for the charging stations to be launched according to the invoice provision strategy of the first operating company and to launch the charging stations to be launched; the invoicing module 503 is used to acquire the invoice request from the requesting user and, in response to the invoice request, to issue an invoice according to the first target invoice provision strategy.
[0080] In this embodiment, charging stations to be launched are periodically identified. After a charging station is identified, the invoice provision strategy of the first operating company to which it belongs is obtained. Further, based on the first operating company's invoice provision strategy, a first target invoice provision strategy corresponding to the charging station to be launched is determined, thus setting the invoice provision strategy for the charging station to be launched and launching the charging station after setting the invoice provision strategy. After the charging station is launched, it will provide charging functionality. After charging, if a user requests an invoice, an invoice will be issued to the requesting user according to the charging station's first target invoice provision strategy. The requesting user can be an individual user, a corporate user, or a user of a downstream channel company, etc.
[0081] In this embodiment, the invoice issuance logic is optimized. Specifically, the invoice provision strategy is determined before the charging station goes online, so that the invoice provision strategy can be configured for the charging station in a timely manner to ensure the accuracy of invoicing.
[0082] Furthermore, the acquisition module 501 is also used to acquire the second operating company's request for a change in the invoice provision strategy; the processing module 502 is also used to determine the second target invoice provision strategy carried in the change request, and change the second operating company's invoice provision strategy to the second target invoice provision strategy.
[0083] Furthermore, the device also includes a sending module for sending a first confirmation request to the terminal device of the finance personnel, the first confirmation request being used to instruct the finance personnel to confirm the strategy for providing a first target invoice or a second target invoice.
[0084] Further, the processing module 502 is specifically configured to: if the first operating company includes an invoice provision strategy, set the invoice provision strategy as the first target invoice provision strategy for the charging station to be launched; the sending module is also configured to: if the first operating company includes multiple invoice provision strategies, send a second confirmation request to the terminal device of the first operating company, the second confirmation request being used to instruct the first operating company to select an invoice provision strategy from the multiple invoice provision strategies; the processing module 502 is specifically configured to: obtain confirmation information fed back by the terminal device of the first operating company, and set the invoice provision strategy indicated in the confirmation information as the first target invoice provision strategy for the charging station to be launched.
[0085] Furthermore, the invoicing strategy of the first operating company includes at least one of the following: the charging application's parent company issues all invoices, the charging application's parent company does not issue any invoices, or the charging application's parent company only issues invoices to enterprises; the business types of the charging application's parent company include at least one of the following: enterprise version, self-operated version, and downstream channel version.
[0086] Furthermore, if the business type corresponding to the requesting user is the enterprise version, then the invoicing module 503 is specifically used for: if the first target invoice provisioning strategy is that the company to which the charging application belongs issues all invoices, then the company to which the application belongs issues an invoice for the requesting user; if the first target invoice provisioning strategy is that the company to which the charging application belongs does not issue any invoices, then no invoice is issued for the requesting user; if the first target invoice provisioning strategy is that the company to which the charging application belongs only issues invoices to enterprises, then the company to which the application belongs issues an invoice for the requesting user.
[0087] Furthermore, if the business type corresponding to the requesting user is a self-operated terminal, then the invoicing module 503 is specifically used for: if the first target invoice provision strategy is that the company to which the charging application belongs issues all invoices, then the company to which the application belongs issues an invoice for the requesting user; if the first target invoice provision strategy is that the company to which the charging application belongs does not issue any invoices, then the first operating company issues an invoice for the requesting user; if the first target invoice provision strategy is that the company to which the charging application belongs only issues invoices to enterprises, then the first operating company issues an invoice for the requesting user.
[0088] Furthermore, if the business type corresponding to the requesting user is the downstream channel version, then the invoicing module 503 is specifically used to: respond to the invoicing request, obtain the invoicing type of the downstream channel version, the invoicing type of the downstream channel version includes issuing invoices and not issuing invoices; and issue invoices according to the invoicing type of the downstream channel version and the first target invoice.
[0089] Furthermore, the invoicing module 503 is specifically used for: if the first target invoice provision strategy is that the company owning the charging application issues all invoices, and the downstream channel version's invoice type is either issuing an invoice or not issuing an invoice, then the company owning the application issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, and the downstream channel version's invoice type is issuing an invoice, then no invoice is issued for the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue any invoices, and the downstream channel version's invoice type is not issuing an invoice, then the first operating company issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the downstream channel version's invoice type is issuing an invoice, then the company owning the application issues an invoice for the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the downstream channel version's invoice type is not issuing an invoice, then the first operating company issues an invoice for the requesting user.
[0090] The invoice-providing device 500 in this embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or any other device besides a terminal.
[0091] The invoice-providing device 500 provided in this application embodiment can achieve... Figure 1 The various processes implemented in the method embodiment for providing invoices will not be described again here to avoid repetition.
[0092] This application also provides an electronic device, such as... Figure 6 As shown, the electronic device 600 includes a processor 601 and a memory 602. The memory 602 stores a program or instructions that can run on the processor 601. When the program or instructions are executed by the processor 601, they implement the various steps of the above-described method embodiment for providing an invoice and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0093] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.
[0094] The memory 602 can be used to store software programs and various data. The memory 602 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 602 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 602 in this embodiment includes, but is not limited to, these and any other suitable types of memory.
[0095] Processor 601 may include one or more processing units; optionally, processor 601 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 601.
[0096] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method embodiment for providing invoices and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0097] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described method embodiments for providing invoices, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0098] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0099] This application also provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described method embodiment for providing an invoice, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0100] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
[0101] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
Claims
1. A method for providing invoices, characterized in that, Applied to a charging application, the method includes: The strategy for identifying charging stations to be launched and obtaining invoices from the first operating company to which the charging stations to be launched belong; Based on the invoice provision strategy of the first operating company, a first target invoice provision strategy is set for the charging stations to be launched, and the charging stations to be launched are then launched. Obtain the invoice request from the requesting user, and in response to the invoice request, issue an invoice according to the first target invoice provision strategy; The invoice provision strategy of the first operating company includes at least one of the following: the company owning the charging application issues all invoices, the company owning the charging application does not issue any invoices, or the company owning the charging application only issues invoices to enterprises; The business type of the company owning the charging application includes at least one of the following: enterprise version, self-operated version, and downstream channel version; If the business type corresponding to the requesting user is Enterprise Edition, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: If the first target invoice provision strategy is for the company to which the charging application belongs to issue all invoices, then the company to which the application belongs shall issue the invoice for the requesting user; If the first target invoice provision strategy is that the company owning the charging application does not issue invoices, then no invoice will be issued for the requesting user; If the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, then the company owning the application will issue an invoice for the requesting user. If the business type corresponding to the requesting user is a self-operated terminal, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: If the first target invoice provision strategy is for the company to which the charging application belongs to issue all invoices, then the company to which the application belongs shall issue the invoice for the requesting user; If the first target invoice provision strategy is that the company owning the charging application does not issue invoices, then the first operating company will issue an invoice for the requesting user. If the first target invoice provision strategy is that the company owning the charging application only issues invoices to businesses, then the first operating company will issue an invoice for the requesting user. If the business type corresponding to the requesting user is the downstream channel version, then in response to the invoice request, an invoice is issued according to the first target invoice provision strategy, including: In response to the invoice request, the invoice type of the downstream channel version is obtained, and the invoice type of the downstream channel version includes issuing an invoice and not issuing an invoice; Invoicing is conducted according to the invoice type of the downstream channel version and the invoice provision strategy of the first target invoice.
2. The method according to claim 1, characterized in that, Also includes: Obtain the second operating company's request for changes to its invoice provision strategy; Determine the second target invoice delivery strategy carried in the change request, and change the second operating company's invoice delivery strategy to the second target invoice delivery strategy.
3. The method according to claim 2, characterized in that, Before setting the first target invoice provision strategy for the charging stations to be launched, or changing the second operating company's invoice provision strategy to the second target invoice provision strategy, the method further includes: A first confirmation request is sent to the terminal device of the finance personnel, the first confirmation request being used to instruct the finance personnel to confirm the strategy for the first target invoice or the second target invoice.
4. The method according to claim 1, characterized in that, Based on the invoice provision strategy of the first operating company, a first target invoice provision strategy is set for the charging stations to be launched, including: If the first operating company includes an invoice provision strategy, then the invoice provision strategy is set as the first target invoice provision strategy for the charging station to be launched; If the first operating company includes multiple invoice delivery strategies, a second confirmation request is sent to the terminal device of the first operating company. The second confirmation request is used to instruct the first operating company to select one invoice delivery strategy from the multiple invoice delivery strategies. Obtain confirmation information from the terminal equipment of the first operating company, and set the invoice provision strategy indicated in the confirmation information as the first target invoice provision strategy for the charging station to be launched.
5. The method according to claim 1, characterized in that, Invoicing is conducted according to the invoice type of the downstream channel version and the first target invoice provision strategy, including: If the first target invoice provision strategy is for the company that owns the charging application to issue all invoices, and the invoice type of the downstream channel version is either to issue an invoice or not to issue an invoice, then the company that owns the application will issue an invoice for the requesting user. If the first target invoice provision strategy is that the company owning the charging application does not issue invoices, and the downstream channel version's invoice type is to issue invoices, then no invoice will be issued to the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue invoices, and the downstream channel version's invoice type is to not issue invoices, then the first operating company will issue an invoice to the requesting user. If the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the downstream channel version's invoice type is "issue invoice", then the company owning the application will issue an invoice to the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the downstream channel version's invoice type is "do not issue invoice", then the first operating company will issue an invoice to the requesting user.
6. An apparatus for providing invoices, characterized in that, For use in charging applications, the device includes: The acquisition module is used to determine the charging stations to be launched and to acquire the invoice provision strategy of the first operating company to which the charging stations to be launched belong; The processing module is used to set the first target invoice provision strategy for the charging station to be launched according to the invoice provision strategy of the first operating company, and to launch the charging station to be launched. The invoicing module is used to obtain the invoice request from the requesting user, and in response to the invoice request, issue an invoice according to the first target invoice provision strategy; The invoice provision strategy of the first operating company includes at least one of the following: the company owning the charging application issues all invoices, the company owning the charging application does not issue any invoices, or the company owning the charging application only issues invoices to enterprises; The business type of the company owning the charging application includes at least one of the following: enterprise version, self-operated version, and downstream channel version; If the business type corresponding to the requesting user is the enterprise version, then the invoicing module is specifically used for: If the first target invoice provision strategy is for the company to which the charging application belongs to issue all invoices, then the company to which the application belongs shall issue the invoice for the requesting user; If the first target invoice provision strategy is that the company owning the charging application does not issue invoices, then no invoice will be issued for the requesting user; If the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, then the company owning the application will issue an invoice for the requesting user. If the business type corresponding to the requesting user is a self-operated terminal, then the invoicing module is specifically used for: If the first target invoice provision strategy is for the company to which the charging application belongs to issue all invoices, then the company to which the application belongs shall issue the invoice for the requesting user; If the first target invoice provision strategy is that the company owning the charging application does not issue invoices, then the first operating company will issue an invoice for the requesting user. If the first target invoice provision strategy is that the company owning the charging application only issues invoices to businesses, then the first operating company will issue an invoice for the requesting user. If the business type corresponding to the requesting user is the downstream channel version, then the invoicing module is specifically used for: In response to the invoice request, the invoice type of the downstream channel version is obtained, and the invoice type of the downstream channel version includes issuing an invoice and not issuing an invoice; Invoicing is conducted according to the invoice type of the downstream channel version and the invoice provision strategy of the first target invoice.
7. The apparatus according to claim 6, characterized in that, The acquisition module is also used to acquire the second operating company's request for a change in its invoice provision strategy; The processing module is further configured to determine the second target invoice provision strategy carried in the change request, and change the second operating company's invoice provision strategy to the second target invoice provision strategy.
8. The apparatus according to claim 7, characterized in that, Also includes: The sending module is used to send a first confirmation request to the terminal device of the finance personnel. The first confirmation request is used to instruct the finance personnel to confirm the strategy provided for the first target invoice or the second target invoice.
9. The apparatus according to claim 6, characterized in that, The processing module is specifically used for: If the first operating company includes an invoice provision strategy, then the invoice provision strategy is set as the first target invoice provision strategy for the charging station to be launched; If the first operating company includes multiple invoice delivery strategies, a second confirmation request is sent to the terminal device of the first operating company. The second confirmation request is used to instruct the first operating company to select one invoice delivery strategy from the multiple invoice delivery strategies. Obtain confirmation information from the terminal equipment of the first operating company, and set the invoice provision strategy indicated in the confirmation information as the first target invoice provision strategy for the charging station to be launched.
10. The apparatus according to claim 6, characterized in that, The invoicing module is specifically used for: If the first target invoice provision strategy is for the company that owns the charging application to issue all invoices, and the invoice type of the downstream channel version is either to issue an invoice or not to issue an invoice, then the company that owns the application will issue an invoice for the requesting user. If the first target invoice provision strategy is that the company owning the charging application does not issue invoices, and the downstream channel version's invoice type is to issue invoices, then no invoice will be issued to the requesting user; if the first target invoice provision strategy is that the company owning the charging application does not issue invoices, and the downstream channel version's invoice type is to not issue invoices, then the first operating company will issue an invoice to the requesting user. If the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the downstream channel version's invoice type is "issue invoice", then the company owning the application will issue an invoice to the requesting user; if the first target invoice provision strategy is that the company owning the charging application only issues invoices to enterprises, and the downstream channel version's invoice type is "do not issue invoice", then the first operating company will issue an invoice to the requesting user.
11. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that run on the processor, the program or instructions, when executed by the processor, implement the steps of the method for providing an invoice as described in any one of claims 1 to 5.
12. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the method for providing an invoice as described in any one of claims 1 to 5.