CN110956512B

CN110956512B - Billing data processing method and device, computer equipment and storage medium

Info

Publication number: CN110956512B
Application number: CN201811134002.4A
Authority: CN
Inventors: 冯健雄; 王跃; 谭名钧; 赖中华; 李昀晟; 桑小康; 陈泽伟; 邱团准; 黄梓健; 姚少棉; 杨慧雯; 周梦莎; 熊祝威; 潘为正
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2018-09-27
Filing date: 2018-09-27
Publication date: 2023-03-10
Anticipated expiration: 2038-09-27
Also published as: CN110956512A

Abstract

The application relates to a billing data processing method, a billing data processing device, a computer readable storage medium and computer equipment, wherein the method comprises the following steps: receiving invoicing request data sent by a server through a first sub-application running on a parent application program, wherein the invoicing request data comprises invoice receiver information; acquiring invoice resource transfer information through a first sub-application; the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier; and sending the invoicing confirmation request to a server so that the server forwards the invoicing confirmation request to an invoicing platform center, generating a corresponding electronic invoice according to the invoicing confirmation request, and sending the electronic invoice to a terminal corresponding to the identifier of the party to which the invoice is pushed. The scheme that this application provided can improve the efficiency of invoicing of electronic invoice.

Description

Billing data processing method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a billing data processing method and apparatus, a computer device, and a storage medium.

Background

The electronic invoice is suitable for industries such as e-commerce, telecommunication, express delivery, public utilities, markets, supermarkets and the like, and can be widely used by taxpayers who issue invoices, self-print the invoice and add value tax common invoices by using a general purpose machine. The gold tax disk or tax control disk is a special device for issuing value-added tax electronic invoices, and is internally provided with a tax control invoicing system. The taxpayer issues an electronic invoice through a single machine version or a server version of a gold tax disk or a tax control disk.

At present, when an invoice person uses a tax-control invoice system such as a gold tax disc or a tax-control disc to issue an electronic invoice, the invoice head-up information of the invoice person needs to be manually input. However, for small and medium-sized enterprises, the method of manually inputting the invoice raising information of the payee by using the tax-controlled invoicing system such as the gold tax tray or the tax-controlled tray by the invoicing personnel not only needs the taxpayer to additionally purchase the tax-controlled invoicing system such as the gold tax tray or the tax-controlled tray, but also needs to develop an interface connected with the tax-controlled invoicing system, so that the development difficulty is high, and the invoicing efficiency is low.

Disclosure of Invention

Therefore, it is necessary to provide a billing data processing method, device, computer device and storage medium for the above technical problems, and in an electronic billing application program, an invoice service provider does not need to additionally purchase a tax-controlled billing system and develop an interface connected with the tax-controlled billing system, thereby reducing the billing difficulty of the electronic billing application program and the billing cost of the invoice service provider, and improving the billing efficiency of electronic billing.

A billing data processing method, the method comprising:

receiving invoicing request data sent by a server through a first sub-application running on a parent application program, wherein the invoicing request data comprises invoice receiver information;

acquiring invoice resource transfer information through a first sub-application;

the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier;

and sending the invoicing confirmation request to a server so as to enable the server and the invoicing platform center to generate a corresponding electronic invoice in an interactive manner, and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

An invoicing data processing system, the system comprising:

the invoice service terminal is used for receiving invoice request data sent by the server through a first sub-application running on a parent application program, the invoice request data comprise invoice receiver information, invoice resource transfer information is obtained through the first sub-application, the first sub-application generates a corresponding invoice confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoice confirmation request carries an invoice pushed party identifier, and the invoice confirmation request is sent to the server.

An invoicing data processing apparatus, the apparatus comprising:

the system comprises a billing request data receiving module, a billing request data receiving module and a billing processing module, wherein the billing request data receiving module is used for receiving billing request data sent by a server through a first sub-application running on a parent application program, and the billing request data comprises invoice receiver information;

the invoice resource transfer information acquisition module is used for acquiring invoice resource transfer information through the first sub-application;

the invoicing confirmation request generation module is used for generating a corresponding invoicing confirmation request by the first sub-application according to the invoice receiver information and the invoice resource transfer information, and the invoicing confirmation request carries an invoice pushed party identifier;

and the invoicing confirmation request sending module is used for sending the invoicing confirmation request to the server so as to enable the server and the invoicing platform center to generate a corresponding electronic invoice in an interactive manner, and sending the electronic invoice to a terminal corresponding to the identifier of the party to which the invoice is pushed.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps when executing the program of:

acquiring invoice resource transfer information through the first sub-application;

and sending the invoice confirmation request to a server so as to enable the server and an invoice platform center to generate a corresponding electronic invoice in an interactive manner, and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of:

According to the invoicing data processing method, the invoicing data processing device, the computer readable storage medium and the computer equipment, the invoicing request data sent by the server is received through the first sub-application running on the parent application program, and the invoicing request data comprises invoice receiver information; acquiring invoice resource transfer information through the first sub-application; the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier; and sending the invoicing confirmation request to a server so that the server generates a corresponding electronic invoice according to the invoicing confirmation request and the invoicing platform center in an interactive manner, and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier. By the aid of a protocol of data interaction agreed by the server and the billing platform center in advance, an invoice service party of the first sub-application running on the parent application program does not need to purchase tax control billing systems such as a gold tax disk or a tax control disk from the billing platform center, and an interface connected with the tax control billing system does not need to be developed, so that the billing difficulty of the electronic invoice and the billing cost of the invoice service party are reduced, and the billing efficiency of the electronic invoice is improved.

Drawings

FIG. 1 is a diagram of an application environment of a billing data processing method in one embodiment;

FIG. 2 is a schematic flow chart diagram of a billing data processing method in one embodiment;

FIG. 2A is a schematic diagram illustrating an interface of a server terminal through a first sub-application running on a parent application in one embodiment;

fig. 2B is an interface diagram illustrating a list of invoice receiver information by the server terminal through an interface of a first sub-application running on the parent application in one embodiment;

FIG. 3 is a schematic flow chart of a billing data processing method according to another embodiment;

FIG. 4 is a schematic flow chart diagram illustrating a billing data processing method according to yet another embodiment;

FIG. 5 is a flowchart showing a processing method of billing data in still another embodiment;

FIG. 5A is a schematic interface diagram illustrating an invoice request data entry interface in one embodiment;

FIG. 5B is a schematic diagram of an embodiment in which a invoice request data entry interface displays candidate invoice recipient information;

FIG. 5C is a schematic diagram illustrating an interface in which an invoice presenter terminal obtains invoice receiver information via a billing request data entry interface in one embodiment;

FIG. 6 is a flowchart illustrating the steps of generating billing request data in one embodiment;

FIG. 7 is a timing diagram of a billing data processing method in one embodiment;

FIG. 8 is a block diagram of an invoicing data processing system in one embodiment;

FIG. 9 is a block diagram of an alternative embodiment billing data processing system;

FIG. 10 is a block diagram showing the structure of an invoice data processing apparatus according to an embodiment;

FIG. 11 is a block diagram of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Fig. 1 is an application environment diagram of an invoicing data processing method in one embodiment. Referring to fig. 1, the billing data processing method is applied to a billing data processing system. The billing data processing system includes a user terminal 110, a server terminal 120, a server 130, and a billing platform center 140. The user terminal 110, the server terminal 120, and the server 130 are connected through a network. The user terminal 110 and the server terminal 120 may be a desktop terminal or a mobile terminal, and the mobile terminal may be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The server 130 may be implemented as a stand-alone server or a server cluster composed of a plurality of servers. The server terminal 120 is an object that provides a service through the first sub-application, such as a merchant that provides an invoicing service, that is, a terminal used by the merchant. The user terminal 110 is a terminal used by a user of the second sub-application. The billing platform center is a server corresponding to an external authority with billing authority. The user terminal 110 may be an invoice pushed party terminal, and the service party terminal 120 may be an invoice service terminal.

Specifically, the user terminal 110 enters the invoicing request data entry interface through the second sub-application running on the parent application, displays candidate invoice receiver information on the invoicing request data entry interface, receives a selection operation acting on the invoicing request data entry interface, determines target invoice receiver information from the candidate invoice receiver information according to the selection operation, generates invoicing request data according to the target invoice receiver information, and sends the invoicing request data to the server 130. The server 130 forwards the billing request data transmitted from the user terminal 110 to the server terminal 120.

The server side terminal 120 receives invoicing request data sent by the server through a first sub-application running on a parent application program, the invoicing request data comprises invoice receiver information, invoice resource transfer information is obtained through the first sub-application, the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoicing confirmation request carries an invoice pushed party identifier, and the invoicing confirmation request is sent to the server 130.

The server 130 forwards the invoice confirmation request to the invoicing platform center 140, generates a corresponding electronic invoice according to the invoice confirmation request, and sends the electronic invoice to a terminal corresponding to the identifier of the party to which the invoice is pushed.

As shown in fig. 2, in one embodiment, a billing data processing method is provided. The embodiment is mainly illustrated by applying the method to the server terminal 120 in fig. 1. Referring to fig. 2, the billing data processing method specifically includes the following steps:

step 202, receiving invoicing request data sent by a server through a first sub-application running on a parent application program, wherein the invoicing request data comprises invoice receiver information.

The parent application is an application program bearing a first sub-application program and provides an environment for realizing the first sub-application program. The parent application is a native application. A native application is an application that can run directly on an operating system. The parent application may be a social application, a dedicated application that specifically supports child applications, a file management application, a mail application, or a gaming application, among others. The Social application program includes an instant messaging application, an SNS (Social Network Service) application, or a live application, and the like. The first sub-application is then an application that can be implemented in the environment provided by the parent application. The first sub-application may specifically be a social application, a file management application, a mail application, or a game application, etc. The parent application may specifically be a WeChat (WeChat) and the corresponding first child application may be referred to as an applet.

The invoicing request data refers to information required for invoicing, the invoicing request data includes but is not limited to invoice receiver information, and the invoice receiver information refers to information related to an invoice receiver. The invoice receiver information includes but is not limited to taxpayers and corresponding tax payment numbers, the taxpayers refer to units or individuals directly bearing tax liabilities on the tax Law stipulation, and the taxpayers refer to units directly bearing tax liabilities on the tax Law stipulation mainly. The tax number corresponding to the taxpayer is the number on the tax registration certificate, each taxpayer has a corresponding unique tax number, and the invoice receiver can be the taxpayer. The billing request data can be stored in the server in advance, and the server sends the billing request data to the server side terminal. Or the user terminal can generate the billing request data through the second sub-application operated by the parent application program, and then the user terminal sends the billing request data to the server and forwards the billing request data to the server side terminal through the server. The server side terminal can receive invoicing request data sent by the server through a first sub-application running on the parent application program, wherein the invoicing request data comprises invoice receiver information.

In a specific embodiment, as shown in fig. 2A, fig. 2A is a schematic diagram illustrating an interface of a server terminal through a first sub-application running on a parent application in one embodiment. The server side terminal can receive the invoicing request data sent by the server through the first sub-application running on the parent application program, wherein the invoicing request data comprises invoice receiver information. As shown in fig. 2A, an invoice receiver information list is displayed on a display interface of the first sub-application, where the invoice receiver information includes invoice header information and invoice header information, such as information of a taxpayer, a corresponding tax number, and a taxpayer registration address. The display interface of the first sub-application shown in fig. 2A further displays a corresponding billing sub-mechanism, and if the a merchant-B area of the first sub-application shown in fig. 2A is clicked, the billing sub-mechanism may be switched.

And step 204, acquiring invoice resource transfer information through the first sub-application.

The invoice resource transfer information refers to relevant information of transfer of invoice resources, and the invoice resource transfer information includes, but is not limited to, invoice resource transfer types, invoice resource transfer amounts and the like. The invoice resource transfer type refers to the category to which the transfer resource belongs, and is related to production and operation items of an invoice receiver, such as catering types, daily necessities types and the like. The invoice resource transfer amount refers to the value spent on transferring the resource, such as the purchase amount. The server side terminal can obtain invoice resource transfer information through a first sub-application scanning graphic code running on the parent application program, wherein the graphic code carries an order identification, and the invoice resource transfer information is obtained through the order identification. Or the service side terminal can input the invoice resource transfer information through an invoice resource transfer information input interface of the first sub-application running on the parent application program so as to obtain the invoice resource transfer information and the like.

In a specific embodiment, the invoice receiver information list is displayed on the server side terminal shown in fig. 2A through an interface of a first sub-application running on a parent application, and the server side terminal may obtain detailed information of the invoice receiver information list through a click operation acting on the invoice receiver information list, as shown in fig. 2B, fig. 2B shows an interface schematic diagram of obtaining invoice resource transfer information through the first sub-application in one embodiment. The invoice resource transfer information, such as the invoice resource transfer value and the invoice resource transfer type, can be entered through the display interface of the detailed information of the invoice receiver information list shown in fig. 2B. If the invoice resource transfer value can be input in the amount shown in fig. 2B, the invoice resource transfer type, such as food, daily general merchandise, fresh food, etc., can be selected from the commodity type shown in fig. 2B.

And step 206, the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier.

The invoice confirming request is used for requesting to confirm the invoice, the invoice confirming request comprises but is not limited to invoice receiver information and invoice resource transfer information, and the invoice confirming request carries an invoice pushed party identifier. The invoice presenter id is a terminal used to uniquely identify an invoice presenter object, for example, a terminal used by a user of the second sub-application, and the invoice presenter id may be used to identify the user terminal 110 in fig. 1, that is, a terminal corresponding to the invoice presenter id may be the user terminal 110 in fig. 1.

Specifically, after receiving the invoice receiver information and the invoice resource transfer information, the first sub-application triggers and generates a corresponding invoice confirmation request through an invoice inlet provided by the first sub-application. The invoicing confirmation request comprises invoice receiver information and invoice resource transfer information. Further, the first sub-application transmits the generated billing confirmation request to the server.

And step 208, sending the invoicing confirmation request to a server so that the server and the invoicing platform center generate a corresponding electronic invoice in an interactive manner, and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

The electronic invoice is uniformly issued to a merchant in an electronic form by the invoicing platform center, the invoice number corresponding to the electronic invoice is uniformly coded in the whole country and is distributed to the merchant by adopting a uniform anti-counterfeiting technology, and the electronic invoice is attached with a signature mechanism of the invoicing platform center. Specifically, the service side terminal is a terminal used by the merchant, the service side terminal sends the generated billing confirmation request to the server through the first sub-application running on the parent application program, and the server forwards the received billing confirmation request to the billing platform center.

The invoicing platform center and the server generate corresponding electronic invoices in an interactive mode, the invoicing platform center can generate the corresponding electronic invoices according to invoicing confirmation requests, then the corresponding electronic invoices are generated according to invoice receiver information and invoice resource transfer information in the invoicing confirmation requests, and the invoicing confirmation requests carry invoice pushed party identifications, so that the invoicing platform terminal sends the generated electronic invoices to terminals corresponding to the invoice pushed party identifications. The electronic invoice generated by the invoicing platform terminal is sent to the terminal corresponding to the invoice pushed party identifier, and the generated electronic invoice can be directly sent to the terminal corresponding to the invoice pushed party identifier, or the generated electronic invoice is firstly forwarded to the server, and then the electronic invoice is sent to the terminal corresponding to the invoice pushed party identifier through the server. The terminal corresponding to the invoice pushed party identifier is a terminal used by an invoice pushed object. And the service side terminal identifies one of the terminals corresponding to the invoice pushed side.

According to the invoicing data processing method, invoicing request data sent by a server is received through a first sub-application running on a parent application program, and the invoicing request data comprises invoice receiver information; acquiring invoice resource transfer information through a first sub-application; the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier; and sending the invoicing confirmation request to a server so that the server forwards the invoicing confirmation request to an invoicing platform center, generating a corresponding electronic invoice according to the invoicing confirmation request, and sending the electronic invoice to a terminal corresponding to the identifier of the party to which the invoice is pushed. By the aid of a protocol of data interaction agreed by the server and the billing platform center in advance, an invoice server of the first sub-application running on the parent application program does not need to additionally purchase tax-control billing systems such as a gold tax disc or a tax-control disc from the billing platform center, and does not need to develop an interface connected with the tax-control billing systems, so that the billing difficulty of the electronic invoice and the billing cost of the invoice server are reduced, and the billing efficiency of the electronic invoice is improved.

In one embodiment, as shown in fig. 3, the billing data processing method further includes:

and step 302, sending a billing authority application request to a server, wherein the billing authority application request carries invoice reimburser information and a billing mechanism identifier so that the server issues a billing authority to a billing mechanism corresponding to the billing mechanism identifier according to the billing authority application request.

The request for applying the invoicing authority is used for applying for obtaining the invoicing authority, and the request for applying the invoicing authority carries invoice reimbursement party information and an invoicing mechanism identifier. The invoice reimbursement party information refers to information required by the invoicing organization for reimbursing the invoice to the invoicing platform center, for example, invoice head-up information of the invoicing organization, and the invoice head-up information includes but is not limited to the name of the invoicing organization and a corresponding tax payment number. The billing mechanism is a mechanism which points to the server to request to obtain the billing authority, and the billing mechanism identifier is a mechanism which is used for uniquely identifying the server to request to obtain the billing authority.

In one embodiment, the server side terminal can trigger and generate a billing authority application request through a billing authority application entrance on a first sub-application running on a parent application program, and sends the billing authority application request to the server. The server negotiates with the billing platform center well in advance, so that the server has billing access capability, namely the billing platform center authorizes the server in advance, and the server obtains billing authority in advance. And once the server receives the request for applying the invoicing authority, issuing the invoicing authority to the invoicing authority corresponding to the invoicing authority identification according to the request for applying the invoicing authority.

In one embodiment, the server side terminal can log in a public platform through registration, and sends an invoicing authority application request to the server through the public platform, similarly, the server negotiates with an invoicing platform center in advance to agree well, and the invoicing platform center authorizes the server in advance, namely the server has the invoicing authority in advance. And once the server receives the request for applying the invoicing authority, issuing the invoicing authority to the invoicing authority corresponding to the invoicing authority identification according to the request for applying the invoicing authority.

And 304, acquiring a target billing sub-mechanism identifier corresponding to the billing mechanism identifier, and issuing a billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identifier.

The target billing sub-mechanism identification is used for uniquely identifying the billing sub-mechanism. Specifically, the server side terminal obtains a target billing sub-mechanism identifier corresponding to the billing mechanism identifier, and issues the billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identifier. Specifically, the target billing sub-mechanism identification corresponding to the billing mechanism identification can be acquired through a first sub-application running on the master application, and the billing authority is issued to the billing sub-mechanism corresponding to the target billing sub-mechanism identification, or the target billing sub-mechanism identification corresponding to the billing mechanism identification can be acquired through a public platform, and the billing authority is issued to the billing sub-mechanism corresponding to the target billing sub-mechanism identification.

In one embodiment, the first sub-application running on the parent application can acquire the target billing sub-mechanism identifier corresponding to the billing mechanism identifier, and issue the billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identifier. If the link with the invoicing authority is sent to the invoicing sub-mechanism corresponding to the target invoicing sub-mechanism identification through the first sub-application, the invoicing sub-mechanism obtains the invoicing authority by triggering the link with the invoicing authority.

In one embodiment, the target billing sub-mechanism identification corresponding to the billing mechanism identification can be acquired through registering and logging in a public platform, and the billing authority is issued to the billing sub-mechanism corresponding to the target billing sub-mechanism identification. For example, the target billing sub-mechanism identifier corresponding to each billing mechanism identifier is set in the public platform billing authority display interface, so that the billing sub-mechanism corresponding to the target billing sub-mechanism identifier has the billing authority.

It should be noted that the terminal sending the request for applying for the billing authority to the server may be a terminal used by the billing authority or a terminal used by the sub-authority. The terminal used by the billing mechanism and the terminal used by the billing sub-mechanism can be the same terminal.

In one embodiment, the billing data processing method further includes: and sending an invoice graphic code generation request to the server, wherein the invoice graphic code generation request carries a target billing sub-mechanism identifier so that the server generates an invoice graphic code corresponding to the target billing sub-mechanism identifier according to the invoice graphic code generation request, and returns the invoice graphic code to a billing sub-mechanism terminal corresponding to the target billing sub-mechanism identifier.

The invoice graphic code is a picture for recording invoice data information by using a black-and-white alternate graphic which is distributed on a plane (two-dimensional direction) according to a certain rule by using a certain specific geometric figure, and can be a two-dimensional code or a bar code and the like. The invoice graphic code generation request is used for requesting generation of the invoice graphic code, and each invoicing sub-mechanism under the invoicing structure has invoicing permission, so that each invoicing sub-mechanism needs to have the corresponding invoice graphic code, and a user of the user terminal can invoice by scanning the invoice graphic code.

In one embodiment, the server side terminal can send an invoice graphic code generation request to the server through a first sub-application running on the parent application, wherein the invoice graphic code generation request carries a target billing sub-mechanism identifier, and the target billing sub-mechanism identifier is used for uniquely identifying the billing sub-mechanism terminal. And after receiving the invoice graphic code generation request, the server generates an invoice graphic code corresponding to each target billing sub-mechanism identifier according to the invoice graphic code generation request, and returns the generated invoice graphic code to the billing sub-mechanism terminal corresponding to each target billing sub-mechanism identifier. Further, the terminal of the billing sub-mechanism can print out the invoice graphic code, and the invoice graphic code is displayed in front of a cash register of a merchant or displayed in a display interface of the first sub-application. The corresponding invoice graphic codes exist in the target invoice sub-mechanism identifications, and the invoice sub-mechanisms with the invoice graphic codes have invoice authority.

In one embodiment, the server side terminal can send an invoice graphic code generation request to the server through a registered login public platform, the server generates an invoice graphic code corresponding to each target billing sub-mechanism identifier according to the invoice graphic code generation request, and the generated invoice graphic code is returned to the billing sub-mechanism terminal corresponding to each target billing sub-mechanism identifier. The invoice graphic codes of different invoicing sub-mechanisms have different invoicing sub-mechanism identifications.

In one embodiment, as shown in fig. 4, the billing data processing method further includes:

step 402, obtaining a public platform registration account.

And step 404, registering an account number through a public platform to log in the public platform, wherein the public platform is used for providing invoicing operation service, and the invoicing operation service comprises invoicing authority application and invoice graphic code generation.

The public platform is a platform for the server to present to the billing organization in a webpage form and select various billing service operations, such as WeChat (WeChat) public platform and WeChat (WeChat) payment merchant platform. The public platform provides various invoicing operation services related to electronic invoicing, wherein the invoicing operation services include but are not limited to invoicing authority application, invoice graphic code generation and the like. Specifically, a service side terminal where the billing mechanism is located can register and log in an account number of a public platform through a display page of the public platform, then log in the public platform through the registered account number which is successfully registered, and trigger corresponding billing operation through selection operation of various billing operation services acting on the display page of the public platform. The selection operation is an operation for selecting various invoicing operation services in a public platform display page, for example, a request for generating invoicing permission application is selected to be triggered so as to obtain corresponding invoicing permission, or a request for generating an invoice graphic code is selected to be triggered so as to generate a corresponding invoice graphic code, and the like. The selection operation may specifically be a touch operation, a physical key operation, or a terminal posture change operation.

In this embodiment, through the invoicing operation service provided by the public platform, the invoice server can directly perform corresponding invoicing operation management on the public platform, such as obtaining an invoicing authority or an invoice graphic code. Therefore, the invoice server can perform various invoicing operation management through the invoicing operation service provided by the public platform, and the access threshold of the invoice server is reduced.

In one embodiment, as shown in fig. 5, the billing data processing method further includes:

step 502, the invoice is triggered by the terminal of the propelling party to enter a invoicing request data entry interface by scanning the current invoice graphic code, and the current invoicing sub-mechanism identification corresponding to the current invoice graphic code is obtained.

And step 504, the invoice pushed party terminal acquires invoice receiver information through an invoicing request data entry interface.

And step 506, the invoice pushed party terminal sends a billing request to the server, wherein the billing request carries billing request data generated according to the invoice receiver information, the current billing sub-mechanism identifier and the invoice pushed party identifier.

The invoice pushed party terminal refers to a terminal where an invoice pushed object is located, and the invoice pushed party terminal may be the user terminal 110 in fig. 1. The current invoice graphic code refers to an invoice graphic code scanned by a second sub-application running on the parent application program currently used by the terminal of the invoice pusher, and if the invoice graphic code displayed by the merchant B in the city a is scanned by the terminal of the invoice pusher through the second sub-application running on the parent application program, the invoice graphic code of the merchant B in the city a can be the current invoice graphic code.

The invoicing request data entry interface is a display interface used for entering invoicing request data by a second sub-application running on the parent application program, and particularly when the invoice is pushed by a terminal of a current invoice through scanning a graphic code of the invoice, the second sub-application triggers to enter the invoicing request data entry interface. The invoice graphic code has corresponding invoice sub-mechanism identification, so that the corresponding current invoice sub-mechanism identification can be obtained by scanning the current invoice graphic code.

The invoice pushed party terminal enters a billing request data entry interface by scanning the current invoice graphic code triggering, and after the current billing sub-mechanism identification corresponding to the current invoice graphic code is obtained, the invoice pushed party terminal can obtain invoice receiving information through the billing request data entry interface. Specifically, target invoice receiver information can be selected from candidate invoice receiver information displayed on the invoicing request data entry interface, wherein the candidate invoice receiver information is obtained by entering information of each invoice receiver in advance through the invoicing request data entry interface, and therefore the candidate invoice receiver information is generated. Further, after the invoice pushed party terminal acquires the invoice receiver information through the invoice request data entry interface, the invoice pushed party terminal can trigger through a second sub-application running on the parent application program to generate an invoice request, and the invoice request is sent to the server. The server receives the billing request and then sends the billing request data generated according to the invoice receiver information to the server terminal.

In one embodiment, the invoice pushed party terminal can scan the current invoice graphic code through a second sub-application running on the parent application program to trigger entering the invoicing request data entry interface, and the current invoice graphic code can be scanned to obtain the corresponding current invoicing sub-mechanism identifier. The billing request data entry interface is shown in fig. 5A, and fig. 5A shows an interface schematic diagram of the billing request data entry interface in one embodiment. As shown in fig. 5A, the billing request data entry interface displays the name of the billing sub-mechanism corresponding to the current billing sub-mechanism identifier, for example, "apply for general tax billing to the store in the area of merchant a-B", and also displays the billing type, for example, individual or unit, and the billing type can be selected through the billing request data entry interface. The invoicing request data entry interface also displays information such as a head-up and an enterprise tax number, and a common head-up trigger control is arranged beside the head-up. Specifically, pre-stored candidate invoice receiver information, that is, candidate invoice head-up information, can be displayed by triggering a common head-up control, as shown in fig. 5B, fig. 5B shows an interface schematic diagram in which invoice request data entry interface displays candidate invoice receiver information in one embodiment, and the candidate invoice head-up information includes company a, company B, company C, and the like.

The method comprises the steps of obtaining invoice receiver information through a selection instruction acting on the candidate invoice receiver information, namely selecting target candidate invoice receiver information designated by the candidate invoice receiver information selection instruction in the displayed candidate invoice receiver information, and determining the target candidate invoice receiver information as invoice receiver information. And after the invoice receiver information is selected from the candidate invoice receiver information, displaying the invoice receiver information at each corresponding display position of the invoicing request data entry interface. As shown in fig. 5C, fig. 5C is a schematic diagram illustrating an interface of an invoice presenter terminal acquiring invoice receiver information through an invoice request data entry interface in one embodiment. As shown in fig. 5C, if the acquired invoice receiver information is company a, the name of company a is displayed in the top of the invoice request data entry interface, the enterprise tax number corresponding to company a is displayed in the enterprise tax number of the invoice request data entry interface, and the registered unit address of company a is displayed in the unit address of the invoice request data entry interface. Finally, a control that triggers the generation of the billing request is provided at the billing request data entry interface, such as "apply for billing" in fig. 5C. The method comprises the steps that a billing request is generated by triggering a 'applying for billing' control, and the invoice pushed party terminal sends the generated billing request to a server, wherein the billing request carries billing request data generated according to invoice receiver information, a current billing sub-mechanism identifier and an invoice pushed party identifier.

Further, after receiving the invoicing request sent by the invoice pushed party terminal, the server forwards the invoicing request data generated according to the invoice receiver information to the server party terminal. The invoice pushed party terminal can place the generated electronic invoice into a storage component of the parent application.

In one embodiment, as shown in fig. 6, the generating of the billing request data includes:

and step 602, the invoice is pushed to the invoice request data entry interface by the pusher terminal through a second sub-application running on the parent application program.

And step 604, displaying the information of the candidate invoice receiver on the invoicing request data entry interface by the invoice pushed party terminal.

And 606, receiving the selection operation acting on the invoicing request data entry interface by the invoice pusher terminal, and determining the target invoice receiver information from the candidate invoice receiver information according to the selection operation.

And step 608, the invoice pushed party terminal generates invoicing request data according to the target invoice receiver information.

The parent application program not only carries the first sub-application program, but also carries the application program of the second sub-application program, and the first sub-application program and the second sub-application program are different sub-application programs. The first sub-application may be a sub-application used by the server terminal, and the second sub-application may be a sub-application used by the user terminal. Specifically, the invoice is pushed by the terminal of the invoice party to enter the invoice request data entry interface through a second sub-application running on the parent application program, candidate invoice receiver information is displayed on the invoice request data entry interface, a selection operation acting on the invoice request data entry interface is received, target invoice receiver information is determined from the candidate invoice receiver information according to the selection operation, and finally invoice request data are generated according to the target invoice receiver information. The candidate invoice receiver information is pre-stored information of each candidate invoice receiver, and can be generated through a billing request data entry interface of a second sub-application running on the parent application.

In one embodiment, the invoice is entered into the invoicing request data entry interface shown in fig. 5A by the pusher terminal through a second sub-application running on the parent application program, the candidate invoice receiver information is triggered and displayed through a related control of the invoicing request data entry interface, the candidate invoice receiver information is triggered and displayed by clicking a common head-up control in the invoicing request data entry interface shown in fig. 5A, and once a click operation of a common head-up acting on the invoicing request data entry interface is detected, the candidate invoice receiver information can be displayed below the invoicing request data entry interface, as shown in fig. 5B. The invoice receiver information is obtained through the selection instruction acting on the candidate invoice receiver information displayed on the invoicing request data entry interface shown in fig. 5B, that is, the target candidate invoice receiver information specified by the candidate invoice receiver information selection instruction is selected in the displayed candidate invoice receiver information. Furthermore, the invoice pushed party terminal generates invoicing request data according to the target invoice receiver information. Specifically, the "apply for invoicing" control shown in fig. 5B may be triggered to generate an invoicing request, where the invoicing request carries invoicing request data generated according to the target invoice receiver information. The invoicing request data includes, but is not limited to, target invoice receiver information and invoice presenter identification.

In a specific embodiment, a billing data processing method is provided, which specifically includes the following steps:

step 702, a server side terminal can send a billing authority application request to a server through a first sub-application running on a parent application program or through logging in a public platform, wherein the billing authority application request carries invoice reimburser information and a billing mechanism identifier, so that the server issues a billing authority to a billing mechanism corresponding to the billing mechanism identifier according to the billing authority application request, wherein the public platform is used for providing billing operation services, the billing operation services comprise billing authority application and invoice graphic code generation, specifically, a public platform registration account needs to be obtained first, and the public platform can be used for providing the billing operation services only by logging in the public platform through the public platform registration account. Furthermore, the server side terminal obtains the target billing sub-mechanism identification corresponding to the billing mechanism identification, and issues the billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identification.

And 704, the server side terminal can send an invoice graphic code generation request to the server through the first sub-application running on the parent application program or through logging in a public platform, wherein the invoice graphic code generation request carries the target billing sub-mechanism identifier, so that the server generates an invoice graphic code corresponding to the target billing sub-mechanism identifier according to the invoice graphic code generation request and returns the invoice graphic code to the billing sub-mechanism terminal corresponding to the target billing sub-mechanism identifier. Similarly, the public platform is used for providing an invoicing operation service, the invoicing operation service comprises invoicing authority application and invoice graphic code generation, and specifically, a public platform registration account needs to be obtained first, and the public platform can be used for providing the invoicing operation service only by logging in the public platform through the public platform registration account. Further, the server side terminal obtains a target billing sub-mechanism identification corresponding to the billing mechanism identification, and issues billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identification.

Step 706, the invoice is triggered by the terminal of the pushing party to enter the invoicing request data entry interface by scanning the current invoice graphic code, the current invoicing sub-mechanism identification corresponding to the current invoice graphic code is obtained, the invoice is obtained by the terminal of the pushing party through the invoicing request data entry interface, the invoice is sent to the server by the terminal of the pushing party to send an invoicing request, and the invoicing request carries invoicing request data generated according to the invoice receiver information, the current invoicing sub-mechanism identification and the invoice being pushed party identification. Further, the server forwards the generated billing request data to the server side terminal.

Step 708, the invoice pushed party terminal enters the invoicing request data entry interface through a second sub-application running on the parent application program, the invoice pushed party terminal displays candidate invoice receiver information on the invoicing request data entry interface, the invoice pushed party terminal receives a selection operation acting on the invoicing request data entry interface, target invoice receiver information is determined from the candidate invoice receiver information according to the selection operation, and the invoice pushed party terminal generates invoicing request data according to the target invoice receiver information. Further, the server forwards the generated billing request data to the server side terminal.

Step 710, the server side terminal receives invoicing request data sent by the server through a first sub-application running on a parent application program, wherein the invoicing request data comprises invoice receiver information;

step 712, the server side terminal obtains invoice resource transfer information through the first sub-application;

step 714, the first sub-application of the server side terminal generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier;

and 716, the server side terminal sends the invoicing confirmation request to the server so that the server forwards the invoicing confirmation request to the invoicing platform center, generates a corresponding electronic invoice according to the invoicing confirmation request, and sends the electronic invoice to the terminal corresponding to the identifier of the party to which the invoice is pushed.

In an application scenario of face-to-face invoicing of a wechat applet, as shown in fig. 7, fig. 7 shows a timing diagram of an invoicing data processing method in one embodiment. And describing the specific principle of the billing data processing method by combining an application scene according to the time sequence diagram of the billing data processing method. The service side terminal can be a terminal used by a merchant, the parent application is a WeChat application program, and the first child application is an invoicing applet used by the merchant, such as an invoicing applet. The invoice pushed party terminal can be a terminal used by a user, the parent application is a WeChat application program, and the second child application is an invoicing applet used by the user, such as an invoicing applet. The first sub-application and the second sub-application can be the same applet, and can jump to different operation interfaces through the user type entering the applet, the user type of the first sub-application is a merchant, and the user type of the second sub-application is a user.

The service side terminal can set a preset approver through an invoicing applet which is operated on WeChat and is suitable for a merchant or logs in a public platform, the preset approver is the name of an organization of an invoicing mechanism, and relevant information of the preset approver is sent to a WeChat background server. And the WeChat background server acquires the corresponding tax payment number according to the related information of the preset approver and binds the preset approver and the corresponding tax payment number. And adding the bound preset approvers and corresponding tax payment numbers into an approver list, wherein the approver list is a list consisting of all approvers bound with the tax payment numbers, and the WeChat background server sends the bound preset approvers and the corresponding tax payment numbers to the corresponding invoicing small programs of the merchants.

Furthermore, the invoicing applet corresponding to the merchant can enter the invoice sub-mechanism identifier (merchant branch identifier) through the invoicing applet corresponding to the merchant running on the WeChat or logging in a public platform, so that the WeChat background server issues the invoicing authority to the merchant branch corresponding to each merchant branch identifier, and meanwhile, the WeChat background server generates the invoicing two-dimensional code corresponding to each merchant branch identifier and returns the generated invoicing two-dimensional code corresponding to each merchant branch identifier to the terminal of the merchant branch corresponding to each merchant branch identifier.

After the terminal of the merchant branch receives the corresponding invoicing two-dimensional code, the invoicing two-dimensional code can be displayed or printed through an invoicing applet corresponding to the merchant of WeChat, and the static invoicing two-dimensional code is displayed in front of a cash register of the merchant branch.

In the process of making an electronic invoice by a user, the user can scan a current invoicing two-dimensional code through an invoicing applet corresponding to the user or scan the current invoicing two-dimensional code through a WeChat scanning function to trigger the current invoicing request data entry interface (invoicing interface of the invoicing applet), obtain a current merchant branch store identification corresponding to the current invoicing two-dimensional code, request a taxpayer head-up list stored in the invoicing applet corresponding to the user by the user to a WeChat background server through the invoicing interface, return the taxpayer head-up list stored in the WeChat application program in advance by the user through the WeChat background server, and particularly display each taxpayer head-up list stored in advance under the invoicing interface. Further, the WeChat background server selects to bill from the returned taxpayer head up list for tax payer head up according to the selection operation through the selection operation of each taxpayer head up list stored in advance and displayed below the invoicing interface. And finally, the invoicing applet corresponding to the user sends an invoicing request to the WeChat background server, the invoicing request carries invoicing request data, current invoicing merchant branch identification and invoicing user terminal identification which are generated by raising a taxpayer according to the selected invoicing, and the WeChat background server forwards the generated invoicing request data to the invoicing applet corresponding to the merchant branch identification.

The micro-letter background server sends the invoicing request to the invoicing small program corresponding to the merchant branch-store identification, the invoicing small program corresponding to the merchant branch-store identification expands information corresponding to the invoicing request on an invoicing small program interface, and specifically, invoicing request data sent by the micro-letter background server can be received through the invoicing small program corresponding to the merchant branch-store identification running on the micro-letter, and the invoicing request data comprises selected invoicing taxpayer head-up information. The invoicing amount and the commodity type consumed by the user, such as food, daily necessities, sports goods and the like, are input through an invoicing request data display interface (the invoicing interface of the invoicing applet) of the invoicing applet corresponding to the merchant branch identification, then an invoicing confirmation request is generated according to the selected invoicing use head-up information and the input invoicing amount and commodity type, specifically, the invoicing confirmation request can be generated through triggering of a control related to the invoicing request data display interface of the invoicing applet corresponding to the merchant branch identification, and the invoicing confirmation request is sent to the WeChat background server.

The WeChat background server forwards the invoicing confirmation request to the invoicing platform center, the invoicing platform center generates a corresponding electronic invoice according to the invoicing confirmation request, and the electronic invoice is sent to the invoicing applet corresponding to the user, for example, the invoicing platform center sends the electronic invoice to the invoicing applet corresponding to the user. After receiving the electronic invoice, the invoicing applet corresponding to the user can display the electronic invoice through the invoicing applet running on the WeChat and store the electronic invoice or store the electronic invoice through related components of the WeChat application program, such as a WeChat card package and the like. The billing platform center also returns the billing state of the electronic invoice to the WeChat background server, the WeChat background server forwards the billing state to the server side terminal, and finally the invoicing applet corresponding to the merchant records the billing state into corresponding billing request data. Wherein the invoicing status is at least one of successful invoicing and failed invoicing. After the corresponding electronic invoice is generated by the invoicing platform center, the electronic invoice can be directly sent to the invoicing applet corresponding to the user, or the invoicing platform center firstly sends the electronic invoice to the WeChat background server and sends the electronic invoice to the invoicing applet corresponding to the user through the WeChat background server.

In one embodiment, there is provided an invoicing data processing method, the method comprising: triggering to enter a billing request data entry interface by scanning a current invoice graphic code, and acquiring a current billing sub-mechanism identifier corresponding to the current invoice graphic code; acquiring invoice receiver information through an invoicing request data entry interface; sending a billing request to a server, wherein the billing request carries billing request data generated according to invoice receiver information, a current billing sub-mechanism identifier and an invoice pushed party identifier; and receiving the electronic invoice sent by the server.

Specifically, the embodiment only adds an execution main body of each step, and the detailed description of each step is already described in the above embodiment, and is not repeated herein.

In one embodiment, obtaining invoice receiver information through an invoicing request data entry interface comprises: entering an invoicing request data entry interface through a second sub-application running on the parent application program; displaying the information of the candidate invoice receivers on an invoicing request data entry interface; receiving a selection operation acting on a billing request data entry interface, and determining target invoice receiver information from the candidate invoice receiver information according to the selection operation; and generating invoice receiver information according to the target invoice receiver information.

In one embodiment, there is provided an invoicing data processing method, the method comprising: the invoice is triggered by a pushing party terminal to enter a billing request data entry interface by scanning a current invoice graphic code, and a current billing sub-mechanism identifier corresponding to the current invoice graphic code is obtained; the invoice pushed party terminal acquires invoice receiver information through an invoice making request data entry interface; the invoice pushed party terminal sends an invoicing request to the server, wherein the invoicing request carries invoicing request data generated according to invoice receiver information, a current invoicing sub-mechanism identifier and an invoice pushed party identifier; the server sends the invoicing request data to an invoice service terminal; the method comprises the steps that an invoice service terminal receives invoicing request data sent by a server through a first sub-application running on a parent application program, the invoicing request data comprise invoice receiver information, invoice resource transfer information is obtained through the first sub-application, the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoicing confirmation request carries an invoice pushed party identifier, and the invoicing confirmation request is sent to the server; the server interacts with the billing platform center according to the billing confirmation request to generate a corresponding electronic invoice, and the billing platform center sends the electronic invoice to the invoice pushed party terminal.

In one embodiment, the billing data processing method further includes: the invoice service terminal sends an invoice authority application request to the server, and the invoice authority application request carries invoice reimbursement party information and an invoice mechanism identifier; the server issues the billing authority to a billing mechanism corresponding to the billing mechanism identification according to the billing authority application request; the invoice service terminal acquires a target billing sub-mechanism identification corresponding to the billing mechanism identification, and issues billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identification.

In one embodiment, the billing data processing method further includes: the invoice service terminal sends an invoice graphic code generation request to the server, and the invoice graphic code generation request carries a target invoicing sub-mechanism identifier; and the server generates an invoice graphic code corresponding to the target billing sub-mechanism identifier according to the invoice graphic code generation request, and returns the invoice graphic code to the billing sub-mechanism terminal corresponding to the target billing sub-mechanism identifier.

In one embodiment, the billing data processing method further includes: the invoice service terminal acquires a public platform registration account; the invoice service terminal logs in the public platform through a public platform registration account, the public platform is used for providing invoicing operation services, and the invoicing operation services comprise invoicing authority application and invoice graphic code generation.

In one embodiment, the method for acquiring the invoice receiver information by the invoice presenter terminal through the invoicing request data entry interface includes: the invoice is pushed by the terminal of the party to enter an invoicing request data entry interface through a second sub-application running on the parent application program; the invoice pushed party terminal displays the information of the candidate invoice receiver on an invoice drawing request data entry interface; the invoice pushed party terminal receives a selection operation acting on an invoicing request data entry interface, and target invoice receiver information is determined from the candidate invoice receiver information according to the selection operation; and the invoice pushed party terminal generates invoice receiver information according to the target invoice receiver information.

It should be understood that the steps in the above-described flowcharts are shown in order as indicated by the arrows, but the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the above-described flowcharts may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least a portion of the sub-steps or stages of other steps.

In one embodiment, there is provided an invoicing data processing system, the system comprising: the invoice service terminal is used for receiving invoicing request data sent by the server through a first sub-application running on a parent application program, the invoicing request data comprise invoice receiver information, invoice resource transfer information is obtained through the first sub-application, the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoicing confirmation request carries an invoice pushed party identifier, and the invoicing confirmation request is sent to the server.

In one embodiment, as shown in fig. 8, there is provided an invoicing data processing system comprising: a server 802 and an invoice service terminal 804, wherein the invoice service terminal 804 may be the service side terminal 120 in fig. 1, and the server 802 may be the server 130 in fig. 1.

The server 802 is configured to send invoicing request data to the invoice service terminal 804.

The invoice service terminal 804 is configured to receive invoicing request data sent by the server through a first sub-application running on a parent application program, where the invoicing request data includes invoice receiver information, obtain invoice resource transfer information through the sub-application, and the sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, where the invoicing confirmation request carries an invoice pushed party identifier, and sends the invoicing confirmation request to the server.

The server 802 is further configured to forward the invoice confirmation request to the invoicing platform center, interact with the invoicing platform center according to the invoice confirmation request to generate a corresponding electronic invoice, and send the electronic invoice to a terminal corresponding to the identifier of the party to which the invoice is pushed by the invoicing platform center.

Specifically, the server 802 sends the invoicing request data to the invoice service terminal 804, where the invoicing request data refers to information required for invoicing, the invoicing request data includes, but is not limited to, invoice receiver information, and the invoice receiver information refers to information related to an invoice receiver. The billing request data can be stored in the server in advance, the server sends the billing request data to the server side terminal, or the user terminal can generate the billing request data through a second sub-application operated by the parent application program, and the user terminal sends the billing request data to the server and forwards the billing request data to the server side terminal through the server. The server side terminal can receive invoicing request data sent by the server through a first sub-application running on the parent application program, wherein the invoicing request data comprises invoice receiver information.

After receiving the invoicing request data sent by the server 802, the invoice service terminal 804 receives the invoicing request data sent by the server 802 through a first sub-application running on a parent application program, the invoicing request data comprises invoice receiver information, then the invoice resource transfer information is obtained through the sub-application, then the sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoicing confirmation request carries an invoice pushed party identifier, and the invoicing confirmation request is sent to the server 802.

The server 802 interacts with the billing platform center to generate a corresponding electronic invoice according to the billing confirmation request, and the billing platform center sends the electronic invoice to the terminal corresponding to the identifier of the invoice pushed party.

In one embodiment, the invoice service terminal is used for sending an invoice authority application request to the server, the invoice authority application request carries invoice reimburser information and an invoice mechanism identifier, the server is used for issuing an invoice authority to an invoice mechanism corresponding to the invoice mechanism identifier according to the invoice authority application request, and the invoice service terminal is further used for acquiring a target invoice authority identifier corresponding to the invoice mechanism identifier and issuing the invoice authority to the invoice authority corresponding to the target invoice authority identifier.

The request for applying the invoicing authority is used for applying for obtaining the invoicing authority, and the request for applying the invoicing authority carries invoice reimbursement party information and an invoicing mechanism identifier. The invoice reimbursement party information refers to information required by the invoicing mechanism to reimburse the invoice to the invoicing platform center, such as invoice head-up information of the invoicing mechanism, wherein the invoice head-up information includes but is not limited to the name of the invoicing mechanism and a corresponding tax receiving number. The billing mechanism is a mechanism which points to the server to request to obtain the billing authority, and the billing mechanism identifier is a mechanism which is used for uniquely identifying the server to request to obtain the billing authority.

In one embodiment, the invoice service terminal 804 may trigger generation of an invoicing permission application request through an invoicing permission application entry on a first sub-application running on a parent application, and send the invoicing permission application request to the server 802. Since the server 802 negotiates with the billing platform center in advance to make a contract, the server 802 has the billing access capability, that is, the billing platform center authorizes the server 802 in advance, and the server 802 obtains the billing right in advance. Once the server 802 receives the request for applying the invoicing authority, the server issues the invoicing authority to the invoicing authority corresponding to the target invoicing authority identification according to the request for applying the invoicing authority.

In one embodiment, the invoice service terminal 804 can log in to the public platform through registration, and send an invoicing authority application request to the server 802 through the public platform, and similarly, the server 802 negotiates with the invoicing platform center in advance to agree well, and the invoicing platform center authorizes the server 802 in advance, that is, the server 802 has the invoicing authority in advance. Once the server 802 receives the request for applying the invoicing authority, the server issues the invoicing authority corresponding to the identifier of the invoicing authority according to the request for applying the invoicing authority.

In one embodiment, the invoice service terminal is further configured to send an invoice graphic code generation request to the server, where the invoice graphic code generation request carries the target billing sub-mechanism identifier, and the server is further configured to generate an invoice graphic code corresponding to the target billing sub-mechanism identifier according to the invoice graphic code generation request, and return the invoice graphic code to the billing sub-mechanism terminal corresponding to the target billing sub-mechanism identifier.

The invoice graphic code is a picture for recording invoice data information by using a black-and-white alternate graphic which is distributed on a plane (two-dimensional direction) according to a certain rule by using a certain specific geometric figure, and can be a two-dimensional code or a bar code and the like. The invoice graphic code generation request is used for requesting generation of the invoice graphic code, and each invoicing sub-mechanism under the invoicing structure flag has an invoicing authority, so that each invoicing sub-mechanism needs to have the corresponding invoice graphic code, and a user of the user terminal can issue invoices by scanning the invoice graphic code.

In one embodiment, the invoice service terminal 804 may send an invoice graphic code generation request to the server 802 through a first sub-application running on the parent application, where the invoice graphic code generation request carries a target billing sub-mechanism identifier, and the target billing sub-mechanism identifier is used to uniquely identify the billing sub-mechanism terminal. After receiving the invoice graphic code generation request, the server 802 generates an invoice graphic code corresponding to each target billing sub-mechanism identifier according to the invoice graphic code generation request, and returns the generated invoice graphic code to the billing sub-mechanism terminal corresponding to each target billing sub-mechanism identifier. Further, the invoice graphic code can be printed out by the terminal of the billing sub-mechanism, and is displayed in front of the merchant cash desk or in the display interface of the first sub-application. The corresponding invoice graphic codes exist in the target invoice sub-mechanism identifications, and the invoice sub-mechanisms with the invoice graphic codes have invoice authority.

In one embodiment, the invoice service terminal 804 may send an invoice graphic code generation request to the server 802 through registering and logging on a public platform, and the server 802 generates an invoice graphic code corresponding to each target billing sub-mechanism identifier according to the invoice graphic code generation request and returns the generated invoice graphic code to the billing sub-mechanism terminal corresponding to each target billing sub-mechanism identifier. The invoice graphic codes of different invoicing sub-mechanisms have different invoicing sub-mechanism identifications.

In one embodiment, the invoice service terminal is further configured to obtain a public platform registration account, and log in the public platform through the public platform registration account, where the public platform is configured to provide an invoicing operation service, and the invoicing operation service includes invoicing authority application and invoice graph code generation.

The public platform is a platform for the server to present to the billing organization in a webpage form and select various billing service operations, such as WeChat (WeChat) public platform. The public platform provides various invoicing operation services related to electronic invoicing, wherein the invoicing operation services comprise but are not limited to invoicing authority application, invoice graphic code generation and the like. Specifically, the invoice service terminal 804 registers an account number of the public platform through a display page of the public platform, then logs in the public platform through the registered account number which is registered successfully, and triggers corresponding invoicing operation through selection operation of various invoicing operation services acting on the display page of the public platform. The selection operation is an operation for selecting various invoicing operation services in a public platform display page, for example, a request for generating invoicing authority application is selected and triggered to obtain corresponding invoicing authority, or a request for generating invoice graphic code is selected and triggered to generate corresponding invoice graphic code, and the like. The selection operation may specifically be a touch operation, a physical key operation, or a terminal posture change operation.

In one embodiment, as shown in fig. 9, the invoicing data processing system further comprises an invoice pushed party terminal 806, wherein the invoice pushed party terminal 806 may be the user terminal 110 in fig. 1, wherein:

the invoice pushed party terminal 806 is used for triggering to enter a invoicing request data entry interface by scanning a current invoice graphic code, acquiring a current invoicing sub-mechanism identifier corresponding to the current invoice graphic code, displaying and acquiring invoice receiver information through the invoicing request data entry interface, and sending an invoicing request to the server, wherein the invoicing request carries invoicing request data generated according to the invoice receiver information, the current invoicing sub-mechanism identifier and the invoice pushed party identifier, and the server 802 is further used for forwarding the generated invoicing request data to the invoice service terminal.

In one embodiment, the invoice presenter terminal 806 may scan the current invoice graphic code through a second sub-application running on the parent application program, trigger the current invoice graphic code to enter a billing request data entry interface, obtain a current billing sub-mechanism identifier corresponding to the current invoice graphic code, display the obtained invoice receiver information through the billing request data entry interface, and send a billing request to the server 802, where the billing request carries billing request data generated according to the invoice receiver information, the current billing sub-mechanism identifier, and the invoice presenter identifier. Further, after receiving the invoicing request sent by the invoice presenter terminal 806, the server 802 forwards the invoicing request data generated according to the invoice receiver information to the invoice service terminal 804. The invoice pushed party terminal can place the generated electronic invoice into a storage component of the parent application.

In another embodiment, the invoice pushed party terminal 806 may further scan a current invoice graphic code through logging in a public platform, trigger to enter a billing request data entry interface, acquire a current billing sub-mechanism identifier corresponding to the current invoice graphic code, display the acquired invoice receiver information through the billing request data entry interface, and send a billing request to the server, where the billing request carries billing request data generated according to the invoice receiver information, the current billing sub-mechanism identifier, and the invoice pushed party identifier. Further, after receiving the invoicing request sent by the invoice presenter terminal 806, the server 802 forwards the invoicing request data generated according to the invoice receiver information to the invoice service terminal 804.

In one embodiment, the invoicing data processing system further comprises an invoice pushed party terminal, the invoice pushed party terminal is used for entering an invoicing request data entry interface through a second sub-application running on a parent application program, displaying candidate invoice receiver information on the invoicing request data entry interface, receiving a selection operation acting on the invoicing request data entry interface, determining target invoice receiver information from the candidate invoice receiver information according to the selection operation, generating invoicing request data according to the target invoice receiver information, sending the invoicing request data to a server, and the server is further used for forwarding the received invoicing request data to an invoice service terminal.

Specifically, the invoice is pushed by the terminal 806 to enter the invoicing request data entry interface through the second sub-application running on the parent application, the candidate invoice receiver information is displayed on the invoicing request data entry interface, the selection operation acting on the invoicing request data entry interface is received, the target invoice receiver information is determined from the candidate invoice receiver information according to the selection operation, the invoicing request data is generated according to the target invoice receiver information, and the invoicing request data is sent to the server 802. The candidate invoice receiver information is pre-stored information of each candidate invoice receiver, and can be generated through a billing request data entry interface of a second sub-application running on the parent application. Where the invoice is entered into the invoicing request data entry interface by the presenter terminal 806 through a second child application running on the parent application may be as shown in figure 5A.

Further, the server 802 forwards the received billing request data to the invoice service terminal 804.

In one embodiment, as shown in fig. 10, there is provided an invoicing data processing apparatus 1000, including:

the invoicing request data receiving module 1002 is configured to receive invoicing request data sent by a server through a first sub-application running on a parent application, where the invoicing request data includes invoice receiver information.

The invoice resource transfer information obtaining module 1004 is configured to obtain the invoice resource transfer information through the first sub-application.

The invoicing confirmation request generating module 1006 is configured to generate, by the first sub-application, a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, where the invoicing confirmation request carries the identifier of the invoice pushed party.

The invoicing confirmation request sending module 1008 is configured to send the invoicing confirmation request to the server, so that the server and the invoicing platform center interact to generate a corresponding electronic invoice, and the electronic invoice is sent to a terminal corresponding to the identifier of the invoice pushed party.

In one embodiment, the billing data processing apparatus 1000 further includes:

the billing authority application request sending module is used for sending a billing authority application request to the server, and the billing authority application request carries invoice reimburser information and a billing mechanism identifier so that the server issues billing authorities to a billing mechanism corresponding to the billing mechanism identifier according to the billing authority application request.

And the target billing sub-mechanism identification acquisition module is used for acquiring the target billing sub-mechanism identification corresponding to the billing mechanism identification and issuing the billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identification.

In one embodiment, the invoicing data processing apparatus 1000 is further configured to send an invoice graphic code generation request to the server, where the invoice graphic code generation request carries the target invoicing sub-mechanism identifier, so that the server generates an invoice graphic code corresponding to the target invoicing sub-mechanism identifier according to the invoice graphic code generation request, and returns the invoice graphic code to the invoicing sub-mechanism terminal corresponding to the target invoicing sub-mechanism identifier.

In one embodiment, the billing data processing apparatus 1000 is further configured to obtain a public platform registration account, and log in the public platform through the public platform registration account, where the public platform is configured to provide a billing operation service, and the billing operation service includes a billing authority application and invoice graphic code generation.

FIG. 11 is a diagram that illustrates an internal structure of the computer device in one embodiment. The computer device may specifically be the server terminal 120 in fig. 1. As shown in fig. 11, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. The memory comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program which, when executed by the processor, causes the processor to implement the invoicing data processing method. The internal memory may also have a computer program stored therein, which when executed by the processor, causes the processor to perform the invoicing data processing method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the billing data processing apparatus provided herein may be implemented in the form of a computer program that is executable on a computer device such as that shown in fig. 11. The memory of the computer device may store various program modules constituting the invoicing data processing apparatus, such as an invoicing request data receiving module, an invoice resource transfer information obtaining module, an invoicing confirmation request generating module, and an invoicing confirmation request sending module shown in fig. 10. The computer program constituted by the respective program modules causes the processor to execute the steps in the invoicing data processing method of each embodiment of the present application described in the present specification.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the above-mentioned invoicing data processing method. Here, the steps of the billing data processing method may be the steps in the billing data processing method of each of the embodiments described above.

In one embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, causes the processor to carry out the steps of the above-mentioned invoicing data processing method. Here, the steps of the billing data processing method may be the steps in the billing data processing method of each of the above embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by a computer program, which may be stored in a non-volatile computer readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct Rambus Dynamic RAM (DRDRAM), and Rambus Dynamic RAM (RDRAM), among others.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, and these are all within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A billing data processing method is applied to an invoice service terminal, and comprises the following steps:

receiving invoicing request data sent by a server of a parent application program through a first child application running on the parent application program, wherein the invoicing request data comprises invoice receiver information;

and sending the invoicing confirmation request to the server so that the server forwards the invoicing confirmation request to an invoicing platform center, wherein the invoicing confirmation request is used for indicating the invoicing platform center to generate a corresponding electronic invoice according to the invoice receiver information and the invoice resource transfer information in the invoicing confirmation request, and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

2. The method of claim 1, further comprising:

sending a billing authority application request to the server, wherein the billing authority application request carries invoice reimburser information and a billing mechanism identifier so that the server issues a billing authority to a billing mechanism corresponding to the billing mechanism identifier according to the billing authority application request;

and acquiring a target billing sub-mechanism identifier corresponding to the billing mechanism identifier, and issuing a billing authority to the billing sub-mechanism corresponding to the target billing sub-mechanism identifier.

3. The method of claim 2, further comprising:

sending an invoice graphic code generation request to the server, wherein the invoice graphic code generation request carries the target billing sub-mechanism identification, so that the server generates an invoice graphic code corresponding to the target billing sub-mechanism identification according to the invoice graphic code generation request, and returns the invoice graphic code to a billing sub-mechanism terminal corresponding to the target billing sub-mechanism identification.

4. The method of claim 1, further comprising:

acquiring a public platform registration account;

and logging in a public platform through the public platform registration account, wherein the public platform is used for providing invoicing operation services, and the invoicing operation services comprise invoicing authority application and invoice graphic code generation.

5. The method of claim 3, further comprising:

an invoice is triggered by a propelling party terminal to enter a billing request data entry interface by scanning a current invoice graphic code, and a current billing sub-mechanism identifier corresponding to the current invoice graphic code is obtained;

the invoice pushed party terminal acquires invoice receiver information through the invoicing request data entry interface;

and the invoice pushed party terminal sends a billing request to the server, wherein the billing request carries the billing request data, the current billing sub-mechanism identifier and the invoice pushed party identifier which are generated according to the invoice receiver information.

6. The method according to claim 1, wherein the generating of the billing request data comprises:

the invoice pushed party terminal enters an invoicing request data entry interface through a second sub-application running on the parent application program;

the invoice pushed party terminal displays candidate invoice receiver information on the invoicing request data entry interface;

the invoice pushed party terminal receives a selection operation acting on the invoicing request data entry interface, and target invoice receiver information is determined from the candidate invoice receiver information according to the selection operation;

and the invoice pushed party terminal generates the invoicing request data according to the target invoice receiver information.

7. A billing data processing method is applied to an invoice pushed party terminal, and comprises the following steps:

triggering an invoicing request data input interface displayed by a second sub-application running on a parent application program by scanning a current invoice graphic code, and acquiring a current invoicing sub-mechanism identifier corresponding to the current invoice graphic code;

acquiring invoice receiver information through the invoicing request data entry interface;

sending a billing request to a server of the parent application program, wherein the billing request carries billing request data generated according to the invoice receiver information, the current billing sub-mechanism identifier and the invoice pushed party identifier; the invoicing request is used for indicating the server to interact with an invoice service terminal to obtain an invoicing confirmation request, and the invoicing confirmation request is forwarded to an invoicing platform center, so that the invoicing platform center generates a corresponding electronic invoice according to the invoice receiver information and the invoice resource transfer information in the invoicing confirmation request;

and after the server receives the electronic invoice sent by the invoicing platform center, receiving the electronic invoice sent by the server.

8. An invoicing data processing method comprises the following steps:

an invoice pushed side terminal is triggered to enter a billing request data entry interface displayed by a second sub-application running on a parent application program by scanning a current invoice graphic code, and a current billing sub-mechanism identifier corresponding to the current invoice graphic code is obtained;

the invoice pushed party terminal obtains invoice receiver information through the invoicing request data entry interface;

the invoice pushed party terminal sends a billing request to a server of the parent application program, wherein the billing request carries the billing request data, the current billing sub-mechanism identification and the invoice pushed party identification which are generated according to the invoice receiver information;

the server sends the invoicing request data to an invoice service terminal;

the invoice service terminal receives invoicing request data sent by a server through a first sub-application running on a parent application program, the invoicing request data comprise invoice receiver information, invoice resource transfer information is obtained through the first sub-application, the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoicing confirmation request carries an invoice pushed party identifier, and the invoicing confirmation request is sent to the server;

the server forwards the billing confirmation request to a billing platform center;

and the invoicing platform center generates a corresponding electronic invoice according to the invoice receiver information and the invoice resource transfer information in the invoicing confirmation request, and sends the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

9. The invoicing data processing system is characterized by comprising a server, an invoice service terminal and an invoicing platform center, wherein:

the server is used for sending invoicing request data to the invoice service terminal;

the invoice service terminal is used for receiving invoicing request data sent by a server of a parent application program through a first sub-application running on the parent application program, wherein the invoicing request data comprise invoice receiver information, invoice resource transfer information is obtained through the first sub-application, the first sub-application generates a corresponding invoicing confirmation request according to the invoice receiver information and the invoice resource transfer information, the invoicing confirmation request carries an invoice pushed party identifier, and the invoicing confirmation request is sent to the server;

the server is also used for receiving the invoicing confirmation request and interacting with the invoicing platform center according to the invoicing confirmation request;

and the invoicing platform center is used for interacting with the server to generate a corresponding electronic invoice and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

10. The system of claim 9, further comprising:

the invoice pushed party terminal is used for entering a billing request data entry interface through scanning a current invoice graphic code, acquiring a current billing sub-mechanism identifier corresponding to the current invoice graphic code, displaying and acquiring invoice receiver information through the billing request data entry interface, and sending a billing request to the server, wherein the billing request carries the billing request data, the current billing sub-mechanism identifier and the invoice pushed party identifier generated according to the invoice receiver information.

11. An invoicing data processing apparatus, characterized in that the apparatus comprises:

the system comprises a billing request data receiving module, a billing request data receiving module and a billing request data receiving module, wherein the billing request data receiving module is used for receiving billing request data sent by a server of a parent application program through a first child application running on the parent application program, and the billing request data comprises invoice receiver information;

the invoicing confirmation request generating module is used for generating a corresponding invoicing confirmation request by the first sub-application according to the invoice receiver information and the invoice resource transfer information, wherein the invoicing confirmation request carries an invoice pushed party identifier;

and the invoicing confirmation request sending module is used for sending the invoicing confirmation request to the server so as to enable the server to forward the invoicing confirmation request to an invoicing platform center, and the invoicing confirmation request is used for indicating the invoicing platform center to generate a corresponding electronic invoice according to the invoice receiver information and the invoice resource transfer information in the invoicing confirmation request and sending the electronic invoice to a terminal corresponding to the invoice pushed party identifier.

12. The apparatus of claim 11, further comprising:

the billing authority application request sending module is used for sending a billing authority application request to the server, wherein the billing authority application request carries invoice reimburser information and a billing mechanism identifier so that the server issues billing authority to a billing mechanism corresponding to the billing mechanism identifier according to the billing authority application request;

13. The apparatus of claim 12, wherein the apparatus is further configured to:

14. The apparatus of claim 11, wherein the apparatus is further configured to:

acquiring a public platform registration account;

and registering an account number through the public platform to log in the public platform, wherein the public platform is used for providing a billing operation service, and the billing operation service comprises a billing authority application and an invoice graphic code generation.

15. A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 8.

16. A computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 8.