Automatic invoicing method, payment and invoicing linkage system, merchant system and user terminal

Abstract

The invention relates to the technical field of invoice management, in particular to an automatic invoicing method, a payment and invoicing linkage system, a merchant system, a user terminal, a computer readable storage medium and a computer program product. The method comprises the following steps: in response to pre-invoicing information received from a merchant, determining and returning a pre-invoicing identifier associated with seller invoicing information of the merchant and the pre-invoicing information to the merchant; in response to a payment request received from the transaction terminal, determining a to-be-invoiced order identifier associated with payment information in the payment request and the pre-invoicing identifier; the payment result and the to-be-invoiced order identifier are returned to the user; in response to a received user invoicing request, determining payment information, pre-invoicing information and seller invoicing information associated with a to-be-invoiced order identifier in the user invoicing request; and sending the determined payment information, the pre-invoicing information and the seller invoicing information together with the buyer invoicing information in the user invoicing request to an invoicing mechanism.

Description

Technical Field

[0001] The present application relates to the technical field of invoice management, and more specifically to an automatic invoicing method, a payment and invoicing linkage system for implementing the method, a merchant system and a user terminal, a computer-readable storage medium and a computer program product for implementing the method. Background Art

[0002] In recent years, with the rapid development of information technology and the continuous advancement of the modernization of national governance capabilities, the field of tax management has also ushered in major opportunities for change. In response to the needs of the times, the State Administration of Taxation has deployed and planned a milestone project - the Golden Tax Phase IV (abbreviated as "Golden Four") information project. The Golden Four Project uses the electronic invoice reform as an engine to promote the comprehensive transformation and upgrading of tax management services through technological innovation. Driven by the Golden Four Project, the popularization and application of electronic invoices have expanded rapidly, becoming an important direction for tax management innovation. The promotion of electronic invoices has not only greatly improved the efficiency of tax management and reduced the costs of both tax authorities and taxpayers, but also provided rich resources for the analysis and application of tax data.

[0003] However, despite various attempts, there are still some urgent problems to be solved in the field of automatic invoicing solutions for electronic invoices. For example, most of the existing automatic invoicing solutions fail to fully realize the seamless connection between payment and invoicing processes, resulting in users and merchants still needing to perform tedious invoicing operations after payment is completed. In addition, there is still much room for improvement in the degree of automation, accuracy of data processing, and user experience of the existing automatic invoicing solutions.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] In order to solve or at least alleviate one or more of the above problems, the embodiments of the present application provide an automatic invoicing method, a payment and invoicing linkage system for implementing the method, a merchant system and a user terminal, a computer-readable storage medium and a computer program product for implementing the method, which realizes the post-payment linkage invoicing function by associating pre-invoicing information, seller's invoicing information and payment information, thereby improving the convenience of invoicing.

[0006] According to a first aspect of the present application, an automatic invoicing method is provided, which is applied to a payment and invoicing linkage system and comprises the following steps: in response to receiving pre-invoicing information from a merchant, determining and returning to the merchant a pre-invoicing identifier associated with the seller's invoicing information and pre-invoicing information of the merchant; in response to receiving a payment request from a transaction terminal, determining an order identifier to be invoiced associated with the payment information and the pre-invoicing identifier in the payment request; returning the payment result and the order identifier to be invoiced to the user; in response to receiving a user invoicing request, determining the payment information, pre-invoicing information and seller's invoicing information associated with the order identifier to be invoiced in the user's invoicing request; and sending the determined payment information, pre-invoicing information and seller's invoicing information together with the buyer's invoicing information in the user's invoicing request to the invoicing agency.

[0007] As an alternative or supplement to the above scheme, the automatic invoicing method according to an embodiment of the present application also includes: receiving an activation request from the merchant, the activation request including the merchant number and the seller's invoicing information of the merchant; and establishing and storing a mapping relationship between the merchant number and the seller's invoicing information.

[0008] As an alternative or supplement to the above scheme, in an automatic invoicing method according to an embodiment of the present application, in response to receiving pre-invoicing information from a merchant, determining and returning to the merchant a pre-invoicing identifier associated with the seller's invoicing information and pre-invoicing information of the merchant includes: determining, based on the mapping relationship, the seller's invoicing information corresponding to the merchant number in the pre-invoicing information; storing the pre-invoicing information and the seller's invoicing information in an associated manner; and generating a unique index number for the stored seller's invoicing information and pre-invoicing information for use as the pre-invoicing identifier.

[0009] As an alternative or supplement to the above solution, in an automatic invoicing method according to an embodiment of the present application, the transaction terminal includes a merchant payment terminal and a user payment terminal.

[0010] As an alternative or supplement to the above solution, when the transaction terminal is a user payment terminal, the automatic invoicing method according to an embodiment of the present application also includes: generating a payment invoicing linkage code based on the pre-invoicing identifier; and sending the payment invoicing linkage code to the merchant for the user to scan the code for payment.

[0011] As an alternative or supplement to the above scheme, in an automatic invoicing method according to an embodiment of the present application, in response to receiving a payment request from a transaction terminal, determining the order identifier to be invoiced associated with the payment information and pre-invoicing identifier in the payment request includes: using the pre-invoicing identifier carried in the payment request as an index number, querying the corresponding sales party invoicing information and pre-invoicing information; storing the payment information carried in the payment request, the queried sales party invoicing information and pre-invoicing information in an associated manner; and generating a unique index number for the stored payment information, sales party invoicing information and pre-invoicing information for use as the order identifier to be invoiced.

[0012] As an alternative or supplement to the above solution, the automatic invoicing method according to an embodiment of the present application also includes: forwarding the payment information carried in the payment request to a corresponding deduction institution; and receiving a payment result for the payment request from the deduction institution.

[0013] As an alternative or supplement to the above scheme, in an automatic invoicing method according to an embodiment of the present application, returning the payment result and the order identifier to be invoiced to the user includes: when the transaction terminal is a user payment terminal, returning the payment result and the order identifier to be invoiced to the transaction terminal; or when the transaction terminal is a merchant payment terminal, returning the payment result and the order identifier to be invoiced to the user's payment application.

[0014] As an alternative or supplement to the above scheme, in an automatic invoicing method according to an embodiment of the present application, in response to receiving a user invoicing request, determining the payment information, pre-invoicing information and seller invoicing information associated with the to-be-invoiced order identifier in the user invoicing request includes: using the to-be-invoiced order identifier carried in the user invoicing request as an index number, querying the corresponding payment information, seller invoicing information and pre-invoicing information.

[0015] As an alternative or supplement to the above scheme, in an automatic invoicing method according to an embodiment of the present application, the seller's invoicing information includes one or more of the following items: seller taxpayer identification number, sales unit name, sales unit telephone number, sales unit address, invoice issuer, payee, and reviewer.

[0016] As an alternative or supplement to the above solution, in an automatic invoicing method according to an embodiment of the present application, the pre-invoicing information includes a merchant number and product information, wherein the product information includes a product name, a tax code, and a tax rate.

[0017] As an alternative or supplement to the above solution, in an automatic invoicing method according to an embodiment of the present application, the payment information includes payment amount, payment method, payment time, and payment account information.

[0018] As an alternative or supplement to the above scheme, the automatic invoicing method according to an embodiment of the present application also includes: receiving the invoicing result from the invoicing agency and saving the invoice data; when the transaction terminal is a user payment terminal, returning the invoicing result to the transaction terminal; when the transaction terminal is a merchant payment terminal, returning the invoicing result to the user's payment application.

[0019] As an alternative or supplement to the above solution, the automatic invoicing method according to an embodiment of the present application also includes: sending the invoice data and the signature verification result to the reimbursement system or a third-party reimbursement platform on the premise of obtaining user authorization.

[0020] According to a second aspect of the present application, a payment and invoicing linkage system is provided, comprising: a memory; a processor; and a computer program stored on the memory and executable on the processor, wherein the execution of the computer program results in the following operations: in response to receiving pre-invoicing information from a merchant, determining and returning to the merchant a pre-invoicing identifier associated with the seller's invoicing information and pre-invoicing information; in response to receiving a payment request from a transaction terminal, determining an order identifier to be invoiced associated with the payment information and the pre-invoicing identifier in the payment request; returning the payment result and the order identifier to be invoiced to the user; in response to receiving a user invoicing request, determining the payment information, pre-invoicing information and seller's invoicing information associated with the order identifier to be invoiced in the user's invoicing request; and sending the determined payment information, pre-invoicing information and seller's invoicing information together with the buyer's invoicing information in the user's invoicing request to the invoicing agency.

[0021] According to a third aspect of the present application, an automatic invoicing method is provided, which is applied to a merchant system including a merchant backend subsystem and a merchant code display terminal, and the method includes the following steps: the merchant backend subsystem sends an activation request to a payment invoicing linkage system, the activation request includes the merchant's merchant number and the seller's invoicing information; the merchant backend subsystem sends pre-invoicing information to the payment invoicing linkage system; the merchant backend subsystem receives a payment invoicing linkage code returned by the payment invoicing linkage system, wherein the payment invoicing linkage code is associated with the seller's invoicing information and the pre-invoicing information of the merchant; and the merchant code display terminal presents the payment invoicing linkage code in a scannable manner for the user to scan the code for payment.

[0022] According to a fourth aspect of the present application, a merchant system is provided, comprising a merchant backend subsystem and a merchant code display terminal, wherein the merchant backend subsystem is configured to: send an activation request to a payment invoicing linkage system, the activation request comprising the merchant's merchant number and the seller's invoicing information; send pre-invoicing information to the payment invoicing linkage system; receive a payment invoicing linkage code returned by the payment invoicing linkage system, wherein the payment invoicing linkage code is associated with the seller's invoicing information and the pre-invoicing information of the merchant; and the merchant code display terminal is configured to: present the payment invoicing linkage code in a scannable manner for the user to scan the code for payment.

[0023] According to a fifth aspect of the present application, an automatic invoicing method is provided, which is applied to a merchant system including a merchant backend subsystem and a merchant payment terminal, and the method includes the following steps: the merchant backend subsystem sends an activation request to a payment invoicing linkage system, the activation request including the merchant's merchant number and the seller's invoicing information; the merchant backend subsystem sends pre-invoicing information to the payment invoicing linkage system; the merchant backend subsystem receives a pre-invoicing identifier returned by the payment invoicing linkage system, wherein the pre-invoicing identifier is associated with the seller's invoicing information of the merchant and the pre-invoicing information; the merchant payment terminal generates payment information in response to user payment behavior; and the merchant payment terminal assembles the payment information and the pre-invoicing identifier into a payment request, and sends the payment request to the payment invoicing linkage system.

[0024] According to the sixth aspect of the present application, a merchant system is provided, comprising a merchant backend subsystem and a merchant payment terminal, wherein the merchant backend subsystem is configured to: send an activation request to a payment and invoicing linkage system, the activation request comprising the merchant's merchant number and the seller's invoicing information; send pre-invoicing information to the payment and invoicing linkage system; receive a pre-invoicing identifier returned by the payment and invoicing linkage system, wherein the pre-invoicing identifier is associated with the seller's invoicing information and the pre-invoicing information of the merchant; and the merchant payment terminal is configured to: generate payment information in response to user payment behavior; assemble the payment information and the pre-invoicing identifier into a payment request, and send the payment request to the payment and invoicing linkage system.

[0025] According to the seventh aspect of the present application, there is provided an automatic invoicing method, which is applied to a user terminal and comprises the following steps: receiving a payment result and an order identifier to be invoiced sent by a payment and invoicing linkage system; presenting the payment result to a user; in response to a user invoicing instruction, assembling the purchaser's invoicing information input by the user and the order identifier to be invoiced into a user invoicing request, and sending the user invoicing request to the payment and invoicing linkage system; and receiving the invoicing result returned by the payment and invoicing linkage system.

[0026] As an alternative or supplement to the above scheme, the automatic invoicing method according to an embodiment of the present application also includes: identifying the payment invoicing linkage code generated by the payment invoicing linkage system, wherein the payment invoicing linkage code carries a pre-invoicing identifier, and the pre-invoicing identifier is associated with the merchant's sales party invoicing information and pre-invoicing information; and in response to the user's payment behavior, sending a payment request to the payment invoicing linkage system, wherein the payment request includes the payment information and the pre-invoicing identifier.

[0027] According to the eighth aspect of the present application, a user terminal is provided, which is configured to: receive a payment result and an order identifier to be invoiced sent by a payment and invoicing linkage system; present the payment result to a user; in response to a user invoicing instruction, assemble the purchaser's invoicing information input by the user and the order identifier to be invoiced into a user invoicing request, and send the user invoicing request to the payment and invoicing linkage system; and receive the invoicing result returned by the payment and invoicing linkage system.

[0028] According to the eighth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium comprises instructions, and the instructions, when run, execute any one of the automatic invoicing methods described in the first aspect, the third aspect, the fifth aspect, and the seventh aspect of the present application.

[0029] According to the ninth aspect of the present application, a computer program product is provided, including a computer program. When the computer program is executed by a processor, it implements any one of the automatic invoicing methods described in the first aspect, the third aspect, the fifth aspect, and the seventh aspect of the present application.

[0030] The automatic invoicing scheme according to one or more embodiments of the present application innovatively uses the pre-invoicing identifier and the order identifier to be invoiced as a bridge between payment and invoicing. Specifically, by associating the pre-invoicing identifier with the seller's invoicing information and pre-invoicing information in the pre-invoicing stage, and associating the order identifier to be invoiced with the payment information and the pre-invoicing identifier in the payment request stage, the matching payment information, pre-invoicing information and seller's invoicing information can be automatically determined through the above-mentioned association relationship in the invoicing request stage, thereby realizing the post-payment linkage invoicing function. This solution realizes automated invoicing for the merchant side, that is, there is no need for the merchant to perform any manual operation, shortens the time cycle from payment to invoicing, and improves the overall business processing efficiency. In addition, the automated invoicing process reduces errors that may be introduced by human operations, such as information mismatches, omissions, etc., and improves the accuracy of invoicing. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and / or other aspects and advantages of the present application will become clearer and easier to understand through the following description of various aspects in conjunction with the accompanying drawings, in which the same or similar units are represented by the same reference numerals. In the accompanying drawings:

[0032] Figure 1 is a schematic flow chart of an automatic invoicing method 10 according to one or more embodiments of the present application;

[0033] Figure 2 A schematic block diagram of a payment and invoicing linkage system 20 according to one or more embodiments of the present application;

[0034] Figure 3 is a schematic block diagram of a merchant system 30 according to one or more embodiments of the present application;

[0035] Figure 4 is a schematic block diagram of a merchant system 40 according to one or more embodiments of the present application;

[0036] Figure 5 is a schematic block diagram of a user terminal 50 according to one or more embodiments of the present application;

[0037] Figure 6 A schematic flowchart of an automatic invoicing method in a payment APP main scanning scenario according to one or more embodiments of the present application;

[0038] Figure 7 A schematic flowchart of an automatic invoicing method in a scenario where a payment APP is scanned according to one or more embodiments of the present application; and

[0039] Figure 8 The present invention is a schematic flowchart of an automatic invoicing method in a card swiping scenario according to one or more embodiments of the present application. DETAILED DESCRIPTION

[0040] The description of the following specific embodiments is merely exemplary in nature and is not intended to limit the disclosed technology or the application and use of the disclosed technology. In addition, it is not intended to be bound by any express or implied theory presented in the aforementioned technical field, background technology or the following specific embodiments.

[0041] In the following detailed description of the embodiments, many specific details are set forth in order to provide a more thorough understanding of the disclosed technology. However, it is apparent to one of ordinary skill in the art that the disclosed technology can be practiced without these specific details. In other instances, well-known features are not described in detail to avoid unnecessarily complicating the description.

[0042] Terms such as "comprising" and "including" indicate that in addition to the units and steps directly and clearly stated in the specification, the technical solution of the present application does not exclude the situation of having other units and steps that are not directly or clearly stated. Terms such as "first" and "second" do not indicate the order of units in terms of time, space, size, etc., but are only used to distinguish between units.

[0043] Hereinafter, various exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings.

[0044] Referring to the accompanying drawings, Figure 1 The following is a schematic flow chart of an automatic invoicing method 10 according to one or more embodiments of the present application. The execution subject of the method 10 is a payment invoicing linkage system, which can be a financial clearing institution, payment service provider, or financial transaction processing institution that can provide payment transfer services and electronic invoice transfer services.

[0045] like Figure 1 As shown, in step S110, in response to receiving the pre-billing information from the merchant, a pre-billing identifier associated with the merchant's sales-side billing information and the pre-billing information is determined and returned to the merchant.

[0046] The pre-invoicing information in this article refers to the information necessary for issuing invoices that the merchant submits to the invoicing system before the payment is completed. Exemplarily, the pre-invoicing information includes the merchant number and product information, wherein the product information includes the product name, tax code, and tax rate.

[0047] In a possible implementation of the present application, the pre-invoicing information includes the seller's invoicing information. The seller's invoicing information herein refers to the relevant information that the seller (i.e., the issuer of the invoice, usually referring to the merchant) needs to provide when issuing the invoice, which is used to be displayed on the invoice. Exemplarily, the seller's invoicing information includes one or more of the following: the seller's taxpayer identification number, the name of the sales unit, the sales unit's telephone number, the sales unit's address, the invoicer, the payee, and the reviewer. In this implementation, the merchant packages the merchant number, product information, and the seller's invoicing information into pre-invoicing information during the pre-invoicing stage, and sends it to the payment invoicing linkage system.

[0048] In another possible implementation of the present application, the merchant uploads the sales party's invoicing information to the payment invoicing linkage system in advance during the authorization stage, so in the pre-invoicing stage, it is only necessary to upload the merchant number and product information, and then the payment invoicing linkage system will associate the merchant number and product information with the pre-stored sales party's invoicing information. In one example, after understanding the specific content and requirements of the post-payment linkage invoicing service provided by the payment invoicing linkage system, the merchant submits an activation request to the payment invoicing linkage system as required; after receiving the merchant's activation request, the payment invoicing linkage system establishes a mapping relationship between the merchant number included in the activation request and the sales party's invoicing information, and stores the mapping relationship locally; after the purchaser consumes at the merchant, the merchant uploads the pre-invoicing information (for example, the merchant number and product information) to the payment invoicing linkage system; the payment invoicing linkage system determines the sales party's invoicing information corresponding to the merchant number in the pre-invoicing information based on the mapping relationship stored in advance.

[0049] In step S110, after the seller's billing information associated with the pre-billing information is determined, a pre-billing identifier associated with the seller's billing information and the pre-billing information of the merchant is determined and returned to the merchant. In one example, the payment and billing linkage system stores the pre-billing information and the seller's billing information in an associated manner, and generates a unique index number for the stored seller's billing information and pre-billing information to be used as a pre-billing identifier.

[0050] In step S120, in response to receiving a payment request from a transaction terminal, an invoicing order identifier associated with the payment information and the pre-invoicing identifier in the payment request is determined.

[0051] It can be understood that since the pre-invoice identifier is associated with the merchant's sales party invoicing information and pre-invoice information, for example, in the above example, the pre-invoice identifier is the unique index number of the sales party invoicing information and the pre-invoice information. Therefore, in the payment request and / or invoice request stage, as long as the pre-invoice identifier is carried in the corresponding request, it can be quickly associated with the corresponding pre-invoice information and sales party invoicing information, thereby eliminating the merchant's manual association, inspection, and confirmation process.

[0052] Exemplarily, after the purchaser completes the payment through the transaction terminal, the transaction terminal (for example, the payment APP on the user's payment terminal or the merchant's payment terminal (for example, the merchant's POS machine or the merchant's code display terminal)) sends a payment request to the payment and invoicing linkage system and carries the pre-invoicing identifier in the payment request.

[0053] This application divides payment scenarios into three categories, namely, payment APP (i.e., application) main scanning scenario, payment APP scanned scenario and card swiping scenario. Taking QR code payment as an example, payment APP main scanning means that the consumer scans the QR code generated by the merchant through his or her smart device, and then confirms the payment amount and completes the payment. In the payment APP main scanning scenario, the consumer actively initiates a payment request, and the merchant passively accepts and confirms the payment result. Payment APP scanned means that the merchant uses the merchant's scanning terminal to scan the QR code generated by the payment APP on the consumer's smart device, and then confirms the payment amount and completes the payment. In the payment APP scanned scenario, the merchant actively initiates a payment request, and the consumer passively accepts and confirms the payment result. The card swiping scenario refers to the merchant actively initiating a payment request, and the consumer confirms the payment amount and completes the payment with a physical bank card. In this article, terminals that can send payment requests to the payment invoicing linkage system are collectively referred to as transaction terminals. Optionally, the transaction terminal is a user payment terminal (for example, a user terminal running a payment APP, such as a smart phone, smart watch, augmented reality (AR) or virtual reality (VR) device) in the payment APP main scanning scenario, and is a merchant payment terminal (for example, a merchant POS machine, a merchant code scanning terminal) in the payment APP scanned scenario and the card swiping scenario.

[0054] In one possible implementation of the present application, in the payment APP main scanning scenario, the payment invoicing linkage system generates a payment invoicing linkage code based on the pre-invoicing identifier, and sends the payment invoicing linkage code to the merchant for the user to scan and pay. After the user uses the code scanning, the payment APP identifies the pre-invoicing identifier in the payment invoicing linkage code and displays the order to the user. After the user selects the card for authentication, the payment APP sends a payment request to the payment invoicing linkage system. In another possible implementation of the present application, in the payment APP scanning scenario, after the user makes a purchase at the merchant, the user shows the payment APP payment code to the merchant. The merchant uses the merchant scanning terminal to scan the payment code and generates payment information, and assembles the payment information and the pre-invoicing identifier into a payment request, and sends the payment request to the payment invoicing linkage system. In another possible implementation of the present application, in a card swiping scenario, after a user makes a purchase at a merchant, the user uses a bank card to swipe the card at the merchant's payment terminal (for example, a merchant POS machine, an all-in-one card swiping and code scanning machine, an aggregate payment device), and the merchant's payment terminal generates payment information and assembles the payment information and the pre-invoicing identifier into a payment request, and sends the payment request to the payment and invoicing linkage system.

[0055] Exemplarily, the above payment information includes payment amount, payment method, payment time, and payment account information.

[0056] In a possible implementation of the present application, after receiving a payment request, the payment and invoicing linkage system uses the pre-invoicing identifier carried in the payment request as an index number to query the corresponding sales party invoicing information and pre-invoicing information, and stores the payment information carried in the payment request, the queried sales party invoicing information and pre-invoicing information in an associated manner, and finally generates a unique index number for the stored payment information, sales party invoicing information and pre-invoicing information to be used as an order identifier to be invoiced. Similarly, since the order identifier to be invoiced is associated with the merchant's sales party invoicing information, pre-invoicing information and payment information, as long as the order identifier to be invoiced is carried in the subsequent invoicing request, it can be quickly associated with the corresponding sales party invoicing information, pre-invoicing information and payment information, thereby eliminating the merchant's manual association, inspection and confirmation process.

[0057] In step S130, the payment result and the order ID to be invoiced are returned to the user.

[0058] In a possible implementation of the present application, after receiving the payment request, the payment invoicing linkage system forwards the payment information carried in the payment request to the corresponding deduction agency for deduction, and receives the payment result for the payment request from the deduction agency, and finally returns the payment result and the order identifier to be invoiced determined in step S120 to the payment channel, for example, the payment APP on the user's payment terminal, the merchant's payment terminal. In a possible implementation of the present application, when the transaction terminal is a user's payment terminal (that is, corresponding to the payment APP main scanning scenario), the payment result and the order identifier to be invoiced are returned to the transaction terminal. In another possible implementation of the present application, when the transaction terminal is a merchant's payment terminal (that is, corresponding to the payment APP being scanned or the card swiping scenario), the payment result and the order identifier to be invoiced are returned to the user's payment APP (for example, WeChat APP, Alipay APP, Cloud QuickPass APP).

[0059] In step S140, in response to receiving the user's invoicing request, the payment information, pre-invoicing information and seller's invoicing information associated with the to-be-invoiced order identifier in the user's invoicing request are determined.

[0060] Exemplarily, after the payment APP pushes the payment result to the user, the purchaser clicks on the payment result notification page to issue the invoice, enters the purchaser's invoicing information such as the invoice header, and submits the invoicing request. The payment APP assembles the order ID to be invoiced and the purchaser's invoicing information into a user invoicing request and sends it to the payment invoicing linkage system. In a possible implementation of the present application, after receiving the user's invoicing request, the payment invoicing linkage system uses the order ID to be invoiced carried in the user's invoicing request as the index number to query the corresponding payment information, the seller's invoicing information, and the pre-invoicing information.

[0061] In step S150, the determined payment information, pre-billing information and seller's billing information are sent to the billing agency together with the buyer's billing information in the user's billing request.

[0062] Optionally, after the invoicing is completed, the invoicing agency (for example, the tax bureau's all-electronic invoice platform) returns the invoicing results and invoice data to the payment invoicing linkage system, and the payment invoicing linkage system saves the invoice data and returns the invoicing results to the payment APP. Optionally, the payment invoicing linkage system can parse the signature value, signature information, electronic seal, public key certificate, original data and original summary value in the invoice according to the latest electronic certificate specifications of the Ministry of Finance, and perform electronic signature verification, and extract the invoice data into the structured data of the account information (XBRL) and store it.

[0063] Optionally, in the subsequent reimbursement circulation stage, when the user needs to reimburse the invoice, the payment and invoicing linkage system can, subject to the user's authorization, pass the invoice data, signature verification results and / or account information structured data to the purchaser's reimbursement system or a third-party reimbursement platform so that it can directly carry out subsequent business processing.

[0064] Figure 2 2 is a schematic block diagram of a payment and invoicing linkage system 20 according to one or more embodiments of the present application. The payment and invoicing linkage system 20 includes a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220. The execution of the computer program 230 enables the following Figure 1 The automatic invoicing method 10 shown is executed. Exemplarily, the payment and invoicing linkage system 20 may be a financial clearing institution, a payment service provider or a financial transaction processing institution that can provide payment transfer services and electronic invoice transfer services.

[0065] Specifically, the payment and invoicing linkage system 20 can be configured to perform the following operations: in response to receiving pre-invoicing information from a merchant, determine and return to the merchant a pre-invoicing identifier associated with the merchant's seller's invoicing information and pre-invoicing information; in response to receiving a payment request from a transaction terminal, determine an order identifier to be invoiced associated with the payment information and pre-invoicing identifier in the payment request; return the payment result and the order identifier to be invoiced to the user; in response to receiving a user's invoicing request, determine the payment information, pre-invoicing information and seller's invoicing information associated with the order identifier to be invoiced in the user's invoicing request; and send the determined payment information, pre-invoicing information and seller's invoicing information together with the buyer's invoicing information in the user's invoicing request to the invoicing agency.

[0066] Optionally, the payment and invoicing linkage system 20 may receive an activation request from a merchant, the activation request including the merchant's merchant number and the seller's invoicing information; and establish and store a mapping relationship between the merchant number and the seller's invoicing information. Optionally, the payment and invoicing linkage system 20 may determine the seller's invoicing information corresponding to the merchant number in the pre-invoicing information based on the mapping relationship; store the pre-invoicing information and the seller's invoicing information in an associated manner; and generate a unique index number for the stored seller's invoicing information and pre-invoicing information to be used as a pre-invoicing identifier. Optionally, the payment and invoicing linkage system 20 may generate a payment and invoicing linkage code based on the pre-invoicing identifier; and send the payment and invoicing linkage code to the merchant for the user to scan the code for payment. Optionally, the payment and invoicing linkage system 20 can use the pre-invoicing identifier carried in the payment request as an index number to query the corresponding sales party invoicing information and pre-invoicing information; store the payment information carried in the payment request, the inquired sales party invoicing information and pre-invoicing information in an associated manner; and generate a unique index number for the stored payment information, sales party invoicing information and pre-invoicing information to be used as the order identifier to be invoiced. Optionally, the payment and invoicing linkage system 20 can forward the payment information carried in the payment request to the corresponding deduction agency; and receive the payment result for the payment request from the deduction agency. Optionally, the payment and invoicing linkage system 20 can return the payment result and the order identifier to be invoiced to the transaction terminal when the transaction terminal is a user payment terminal; or return the payment result and the order identifier to be invoiced to the user's payment application when the transaction terminal is a merchant payment terminal. Optionally, the payment and invoicing linkage system 20 can use the order identifier to be invoiced carried in the user's invoicing request as an index number to query the corresponding payment information, sales party invoicing information and pre-invoicing information. Optionally, the payment and invoicing linkage system 20 may receive the invoicing result from the invoicing institution and save the invoice data; if the transaction terminal is a user payment terminal, the invoicing result is returned to the transaction terminal; if the transaction terminal is a merchant payment terminal, the invoicing result is returned to the user's payment application. Optionally, the payment and invoicing linkage system 20 may send the invoice data and the signature verification result to the reimbursement system or a third-party reimbursement platform on the premise of obtaining user authorization.

[0067] Figure 3 FIG. 3 is a schematic block diagram of a merchant system 30 according to one or more embodiments of the present application. Figure 3 As shown, the merchant system 30 includes a merchant backend subsystem 310 and a merchant code display terminal 320. The merchant system 30 is suitable for the payment APP main scanning scenario described above.

[0068] The merchant backend subsystem 310 is configured to: send an activation request to the payment invoicing linkage system, the activation request includes the merchant's merchant number and the seller's invoicing information; send pre-invoicing information to the payment invoicing linkage system; receive the payment invoicing linkage code returned by the payment invoicing linkage system, wherein the payment invoicing linkage code is associated with the seller's invoicing information and pre-invoicing information. The merchant code display terminal 320 is configured to present the payment invoicing linkage code in a scannable manner for the user to scan the code for payment.

[0069] Figure 4 FIG. 4 is a schematic block diagram of a merchant system 40 according to one or more embodiments of the present application. Figure 4 As shown, the merchant system 40 includes a merchant backend subsystem 410 and a merchant payment terminal 420. The merchant system 30 is applicable to the payment APP scanning scenario and the card swiping scenario described above. Exemplarily, in the payment APP scanning scenario, the merchant payment terminal 420 is a merchant scanning terminal (for example, a handheld scanner, a desktop scanner, an integrated card scanning machine, an aggregate payment device, etc.); in the card swiping scenario, the merchant payment terminal 420 is a merchant POS machine, an integrated card scanning machine or an aggregate payment device.

[0070] The merchant backend subsystem 410 is configured to: send an activation request to the payment and invoicing linkage system, the activation request includes the merchant's merchant number and the seller's invoicing information; send pre-invoicing information to the payment and invoicing linkage system; receive a pre-invoicing identifier returned by the payment and invoicing linkage system, wherein the pre-invoicing identifier is associated with the seller's invoicing information and the pre-invoicing information. The merchant payment terminal 420 is configured to: generate payment information in response to user payment behavior; assemble the payment information and the pre-invoicing identifier into a payment request, and send the payment request to the payment and invoicing linkage system.

[0071] Figure 5It is a schematic block diagram of a user terminal 50 according to one or more embodiments of the present application. Exemplarily, the user terminal 50 includes, but is not limited to: a smart phone, a tablet computer, a laptop computer, a desktop computer, an in-vehicle infotainment system, an AR device or a VR device, or any smart device that can receive user instructions and interact with the user. The user terminal 50 can be applied to the payment APP main scanning scenario, the payment APP scanned scenario and the card swiping scenario described above. Exemplarily, in the payment APP main scanning scenario or the payment APP scanned scenario, the user terminal 50 includes a payment APP (e.g., WeChat APP, Alipay APP, Cloud QuickPass APP) running thereon; in the card swiping scenario, the user terminal 50 includes an invoicing APP with an invoicing function running thereon, for example, Cloud QuickPass APP.

[0072] The user terminal 50 is configured to: receive the payment result and the identification of the order to be invoiced sent by the payment and invoicing linkage system; present the payment result to the user; in response to the user's invoicing instruction, assemble the purchaser's invoicing information and the identification of the order to be invoiced input by the user into a user invoicing request, and send the user invoicing request to the payment and invoicing linkage system; and receive the invoicing result returned by the payment and invoicing linkage system.

[0073] In the payment APP main scanning scenario, the user terminal 50 is also configured to: use the payment APP to identify the payment invoicing linkage code generated by the payment invoicing linkage system, wherein the payment invoicing linkage code carries a pre-invoicing identifier, and the pre-invoicing identifier is associated with the merchant's sales party invoicing information and pre-invoicing information; and in response to the user's payment behavior, send a payment request to the payment invoicing linkage system via the payment APP, wherein the payment request includes the payment information and the pre-invoicing identifier.

[0074] Figure 6 The present invention is a schematic flowchart of an automatic invoicing method in a payment APP main scanning scenario according to one or more embodiments of the present application.

[0075] like Figure 6As shown, in step S601, after the user makes a purchase at a merchant, the merchant (e.g., the merchant backend subsystem 310) sends the pre-invoicing information and the sales party invoicing information to the payment invoicing linkage system (e.g., the payment invoicing linkage system 20). In step S603, the payment invoicing linkage system generates and returns to the merchant a payment invoicing linkage code associated with the sales party invoicing information and the pre-invoicing information of the merchant. In step S605, the merchant (e.g., the merchant code display terminal 320) presents the payment invoicing linkage code to the user. In step S607, the user uses the payment APP to scan the code for payment linkage invoicing, and sends a payment request to the payment invoicing linkage system, wherein the payment request includes the payment information and the pre-invoicing identifier. In step S609, the payment invoicing linkage system determines the to-be-invoiced order identifier associated with the payment information and the pre-invoicing identifier in the payment request. In step S611, the payment invoicing linkage system forwards the payment information to the corresponding deduction agency. In step S613, the deduction institution returns the payment result to the payment and invoicing linkage system. In step S615, the payment and invoicing linkage system returns the payment result and the order ID to be invoiced to the user's payment APP. In step S617, the payment APP pushes the payment result to the user. After the user clicks to issue an invoice on the notification page of the payment result and enters the purchaser's invoicing information such as the invoice header, the payment APP assembles the purchaser's invoicing information and the order ID to be invoiced entered by the user into a user's invoicing request. In step S619, the payment APP sends the user's invoicing request to the payment and invoicing linkage system. In step S621, the payment and invoicing linkage system determines the payment information, pre-invoicing information and the seller's invoicing information associated with the order ID to be invoiced in the user's invoicing request. In step S623, the payment and invoicing linkage system sends the determined payment information, pre-invoicing information and the seller's invoicing information together with the purchaser's invoicing information in the user's invoicing request to the invoicing institution. In step S625, the invoicing institution returns the invoicing result to the payment and invoicing linkage system. In step S627, the payment and invoicing linkage system saves the invoice data and returns the invoicing result to the payment APP.

[0076] Figure 7 The present invention is a schematic flowchart of an automatic invoicing method in a scenario where a payment APP is scanned according to one or more embodiments of the present application.

[0077] like Figure 7As shown, in step S701, after the user makes a purchase at the merchant, the merchant (e.g., the merchant backend subsystem 410) sends the pre-invoicing information and the seller's invoicing information to the payment invoicing linkage system (e.g., the payment invoicing linkage system 20). In step S703, the payment invoicing linkage system generates and returns to the merchant a pre-invoicing identifier associated with the seller's invoicing information and the pre-invoicing information of the merchant. In step S705, after the user makes a purchase at the merchant, the merchant (e.g., the merchant's payment terminal 420, such as the merchant's code scanning terminal) scans the payment code to identify the payment information. In step S707, the merchant assembles the payment information and the pre-invoicing identifier into a payment request and sends the payment request to the payment invoicing linkage system. In step S709, the payment invoicing linkage system determines the to-be-invoiced order identifier associated with the payment information and the pre-invoicing identifier in the payment request. In step S711, the payment invoicing linkage system forwards the payment information to the corresponding deduction agency. In step S713, the deduction agency returns the payment result to the payment invoicing linkage system. In step S715, the payment invoicing linkage system returns the payment result and the order identifier to be invoiced to the user's payment APP. Optionally, step S715 also includes the payment invoicing linkage system returning the payment result to the merchant. In step S717, the payment APP pushes the payment result to the user. After the user clicks to issue an invoice on the notification page of the payment result and enters the purchaser's invoicing information such as the invoice header, the payment APP assembles the purchaser's invoicing information entered by the user and the order identifier to be invoiced into a user's invoicing request. In step S719, the payment APP sends the user's invoicing request to the payment invoicing linkage system. In step S721, the payment invoicing linkage system determines the payment information, pre-invoicing information and the seller's invoicing information associated with the order identifier to be invoiced in the user's invoicing request. In step S723, the payment invoicing linkage system sends the determined payment information, pre-invoicing information and the seller's invoicing information together with the purchaser's invoicing information in the user's invoicing request to the invoicing agency. In step S725, the invoicing agency returns the invoicing result to the payment invoicing linkage system. In step S727, the payment invoicing linkage system saves the invoice data and returns the invoicing result to the payment APP.

[0078] Figure 8 The present invention is a schematic flowchart of an automatic invoicing method in a card swiping scenario according to one or more embodiments of the present application.

[0079] like Figure 8As shown, in step S801, after the user makes a purchase at a merchant, the merchant (e.g., the merchant backend subsystem 410) sends the pre-invoicing information and the sales-side invoicing information to the payment invoicing linkage system (e.g., the payment invoicing linkage system 20). In step S803, the payment invoicing linkage system generates and returns to the merchant a pre-invoicing identifier associated with the sales-side invoicing information and the pre-invoicing information of the merchant. In step S805, after the user makes a purchase at the merchant, he uses a bank card to pay at the merchant's payment terminal (e.g., the merchant's payment terminal 420, such as a merchant's POS machine). In step S807, the merchant's payment terminal assembles the payment information and the pre-invoicing identifier into a payment request and sends the payment request to the payment invoicing linkage system. In step S809, the payment invoicing linkage system determines the to-be-invoiced order identifier associated with the payment information and the pre-invoicing identifier in the payment request. In step S811, the payment invoicing linkage system forwards the payment information to the corresponding deduction agency. In step S813, the deduction agency returns the payment result to the payment invoicing linkage system. In step S815, the payment invoicing linkage system returns the payment result and the order ID to be invoiced to the user's invoicing APP (for example, Cloud QuickPass APP) (the user needs to bind the card in the invoicing APP in advance). Optionally, step S815 also includes the payment invoicing linkage system returning the payment result to the merchant. In step S817, the invoicing APP pushes the payment result to the user. The user clicks to invoice on the notification page of the payment result. After entering the purchaser's invoicing information such as the invoice header, the invoicing APP assembles the purchaser's invoicing information entered by the user and the order ID to be invoiced into a user invoicing request. In step S819, the invoicing APP sends the user's invoicing request to the payment invoicing linkage system. In step S821, the payment invoicing linkage system determines the payment information, pre-invoicing information and selling party invoicing information associated with the order ID to be invoiced in the user's invoicing request. In step S823, the payment and invoicing linkage system sends the confirmed payment information, pre-invoicing information and seller invoicing information together with the buyer invoicing information in the user invoicing request to the invoicing agency. In step S825, the invoicing agency returns the invoicing result to the payment and invoicing linkage system. In step S827, the payment and invoicing linkage system saves the invoice data and returns the invoicing result to the invoicing APP.

[0080] For the specific implementation of steps S601-S627, S701-S727, S801-S827, please refer to the above description of method 10, merchant systems 30 and 40, and user terminal 50, which will not be repeated here.

[0081] According to one or more embodiments of the present application, the automatic invoicing method (for example, Figure 1 , Figure 6 , Figure 7 or Figure 8The automatic invoicing method shown in the figure innovatively uses the pre-invoicing identifier and the order identifier to be invoiced as a bridge between payment and invoicing. Specifically, by associating the pre-invoicing identifier with the seller's invoicing information and the pre-invoicing information in the pre-invoicing stage, and associating the order identifier to be invoiced with the payment information and the pre-invoicing identifier in the payment request stage, the matching payment information, pre-invoicing information and seller's invoicing information can be automatically determined through the above-mentioned association in the invoicing request stage, thereby realizing the post-payment linkage invoicing function. This solution realizes automated invoicing for the merchant side, that is, there is no need for the merchant to perform any manual operation, shortens the time cycle from payment to invoicing, and improves the overall business processing efficiency. In addition, the automated invoicing process reduces errors that may be introduced by human operations, such as information mismatches, omissions, etc., and improves the accuracy of invoicing.

[0082] In addition, the present application can also be implemented as a computer-readable storage medium, in which a program for causing a computer to execute the following steps is stored. Figure 1 , Figure 6 , Figure 7 or Figure 8 Here, as the computer-readable storage medium, various computer-readable storage media such as disks (e.g., magnetic disks, optical disks, etc.), cards (e.g., memory cards, optical cards, etc.), semiconductor memories (e.g., ROMs, nonvolatile memories, etc.), and tapes (e.g., magnetic tapes, cassette tapes, etc.) can be used.

[0083] The present disclosure may also be implemented as a computer program product, which includes a computer program. When the computer program is executed by a processor, the following Figure 1 , Figure 6 , Figure 7 or Figure 8 The steps in the method are shown in the procedure.

[0084] In the applicable situation, hardware, software or a combination of hardware and software can be used to realize the various embodiments provided by the application. Moreover, in the applicable situation, without departing from the scope of the application, the various hardware components and / or software components set forth herein can be combined into a composite component comprising software, hardware and / or both. In the applicable situation, without departing from the scope of the application, the various hardware components and / or software components set forth herein can be divided into subcomponents comprising software, hardware or both. In addition, in the applicable situation, it is contemplated that the software component can be implemented as a hardware component, and vice versa.

[0085] Software according to the present application (such as program code and / or data) can be stored on one or more computer-readable storage media. It is also contemplated that the software identified herein can be implemented using one or more general or special-purpose computers and / or computer systems, networked and / or otherwise. Where applicable, the order of the various steps described herein can be changed, combined into composite steps, and / or divided into sub-steps to provide the features described herein.

[0086] The embodiments and examples set forth herein are provided to best illustrate embodiments according to the present application and its specific applications, and thereby enable those skilled in the art to implement and use the present application. However, those skilled in the art will appreciate that the above description and examples are provided only for ease of illustration and example. The description set forth is not intended to cover all aspects of the present application or to limit the present application to the precise form disclosed.

Claims

1. An automatic invoicing method, characterized in that: The method is applied to a payment and invoicing linkage system and comprises the following steps: In response to receiving pre-billing information from a merchant, determining and returning to the merchant a pre-billing identifier associated with the merchant's sales-side billing information and the pre-billing information; In response to receiving a payment request from a transaction terminal, determining a to-be-invoiced order identifier associated with the payment information and the pre-invoicing identifier in the payment request; Return the payment result and the order ID to be invoiced to the user; In response to receiving a user billing request, determining payment information, pre-billing information, and seller billing information associated with a to-be-billed order identifier in the user billing request; and The determined payment information, pre-billing information and seller's billing information are sent to the billing agency together with the buyer's billing information in the user's billing request.

2. The automatic invoicing method according to claim 1, characterized in that: The method further comprises: receiving an activation request from the merchant, the activation request including the merchant number and the seller's invoicing information; and A mapping relationship between the merchant number and the seller's invoicing information is established and stored.

3. The automatic invoicing method according to claim 2, characterized in that: In response to receiving pre-billing information from a merchant, determining and returning to the merchant a pre-billing identifier associated with the merchant's sales party billing information and the pre-billing information includes: According to the mapping relationship, determine the sales party invoicing information corresponding to the merchant number in the pre-invoicing information; storing the pre-billing information and the seller's billing information in an associated manner; and A unique index number is generated for the stored sales party billing information and pre-billing information to be used as the pre-billing identifier.

4. The automatic invoicing method according to claim 1, characterized in that: The transaction terminal includes a merchant payment terminal and a user payment terminal.

5. The automatic invoicing method according to claim 4, characterized in that: In the case where the transaction terminal is a user payment terminal, the method further includes: Generate a payment and billing linkage code based on the pre-billing identifier; and The payment invoicing linkage code is sent to the merchant for the user to scan and pay.

6. The automatic invoicing method according to claim 3, characterized in that: In response to receiving a payment request from a transaction terminal, determining a to-be-invoiced order identifier associated with payment information and a pre-invoicing identifier in the payment request includes: Using the pre-invoicing identifier carried in the payment request as an index number, query the corresponding sales party's invoicing information and pre-invoicing information; storing the payment information carried in the payment request, the queried seller's billing information and the pre-billing information in an associated manner; and A unique index number is generated for the stored payment information, seller's billing information and pre-billing information to be used as the identification of the order to be invoiced.

7. The automatic invoicing method according to claim 1, characterized in that: The method further comprises: Forwarding the payment information contained in the payment request to the corresponding deduction institution; and A payment result for the payment request is received from the debiting institution.

8. The automatic invoicing method according to claim 1, characterized in that: Returning the payment result and the order ID to be invoiced to the user includes: In the case where the transaction terminal is a user payment terminal, returning the payment result and the to-be-invoiced order identifier to the transaction terminal; or In the case where the transaction terminal is a merchant payment terminal, the payment result and the to-be-invoiced order identifier are returned to the user's payment application.

9. The automatic invoicing method according to claim 6, characterized in that: In response to receiving a user invoicing request, determining payment information, pre-invoicing information, and seller invoicing information associated with an order identifier to be invoiced in the user invoicing request includes: The order ID to be invoiced carried in the user's invoicing request is used as the index number to query the corresponding payment information, the seller's invoicing information and the pre-invoicing information.

10. The automatic invoicing method according to claim 1, characterized in that: The invoicing information of the seller includes one or more of the following items: the seller's taxpayer identification number, the name of the selling unit, the selling unit's telephone number, the selling unit's address, the invoice issuer, the payee, and the reviewer.

11. The automatic invoicing method according to claim 1, characterized in that: The pre-invoicing information includes a merchant number and product information, wherein the product information includes product name, tax code, and tax rate.

12. The automatic invoicing method according to claim 1, characterized in that: The payment information includes payment amount, payment method, payment time, and payment account information.

13. The automatic invoicing method according to claim 1, characterized in that: The method further comprises: Receive the invoicing result from the invoicing agency and save the invoice data; In the case where the transaction terminal is a user payment terminal, returning the invoicing result to the transaction terminal; In the case where the transaction terminal is a merchant payment terminal, the invoicing result is returned to the user's payment application.

14. The automatic invoicing method according to claim 13, characterized in that: The method further comprises: With the user's authorization, the invoice data and signature verification results will be sent to the reimbursement system or a third-party reimbursement platform.

15. A payment and invoicing linkage system, characterized in that: Include: Memory; Processor; and A computer program stored on the memory and executable on the processor, the execution of which results in the following operations: In response to receiving pre-billing information from a merchant, determining and returning to the merchant a pre-billing identifier associated with the merchant's sales-side billing information and the pre-billing information; In response to receiving a payment request from a transaction terminal, determining a to-be-invoiced order identifier associated with the payment information and the pre-invoicing identifier in the payment request; Return the payment result and the order ID to be invoiced to the user; In response to receiving a user invoicing request, determining payment information, pre-invoicing information, and seller invoicing information associated with an order identifier to be invoiced in the user invoicing request; as well as The determined payment information, pre-billing information and seller's billing information are sent to the billing agency together with the buyer's billing information in the user's billing request.

16. The payment and invoicing linkage system according to claim 15, characterized in that: The execution of the computer program also results in the following operations: receiving an activation request from the merchant, the activation request including the merchant number and the seller's invoicing information; and A mapping relationship between the merchant number and the seller's invoicing information is established and stored.

17. The payment and invoicing linkage system according to claim 16, characterized in that: In response to receiving pre-billing information from a merchant, determining and returning to the merchant a pre-billing identifier associated with the merchant's sales party billing information and the pre-billing information includes: According to the mapping relationship, determine the sales party invoicing information corresponding to the merchant number in the pre-invoicing information; storing the pre-billing information and the seller's billing information in an associated manner; and A unique index number is generated for the stored sales party billing information and pre-billing information to be used as the pre-billing identifier.

18. The payment and invoicing linkage system according to claim 15, characterized in that: The transaction terminal includes a merchant payment terminal and a user payment terminal.

19. The payment and invoicing linkage system according to claim 18, characterized in that: In the case where the transaction terminal is a user payment terminal, the execution of the computer program further results in the following operations: Generate a payment and billing linkage code based on the pre-billing identifier; and The payment invoicing linkage code is sent to the merchant for the user to scan and pay.

20. The payment and invoicing linkage system according to claim 17, characterized in that: In response to receiving a payment request from a transaction terminal, determining a to-be-invoiced order identifier associated with payment information and a pre-invoicing identifier in the payment request includes: Using the pre-invoicing identifier carried in the payment request as an index number, query the corresponding sales party's invoicing information and pre-invoicing information; storing the payment information carried in the payment request, the queried seller's billing information and the pre-billing information in an associated manner; and A unique index number is generated for the stored payment information, seller's billing information and pre-billing information to be used as the identification of the order to be invoiced.

21. The payment and invoicing linkage system according to claim 15, characterized in that: The execution of the computer program also results in the following operations: Forwarding the payment information contained in the payment request to the corresponding deduction institution; and A payment result for the payment request is received from the debiting institution.

22. The payment and invoicing linkage system according to claim 15, characterized in that: Returning the payment result and the order ID to be invoiced to the user includes: In the case where the transaction terminal is a user payment terminal, returning the payment result and the to-be-invoiced order identifier to the transaction terminal; or In the case where the transaction terminal is a merchant payment terminal, the payment result and the to-be-invoiced order identifier are returned to the user's payment application.

23. The payment and invoicing linkage system according to claim 20, characterized in that: In response to receiving a user invoicing request, determining payment information, pre-invoicing information, and seller invoicing information associated with an order identifier to be invoiced in the user invoicing request includes: The order ID to be invoiced carried in the user's invoicing request is used as the index number to query the corresponding payment information, the seller's invoicing information and the pre-invoicing information.

24. The payment and invoicing linkage system according to claim 15, characterized in that: The invoicing information of the seller includes one or more of the following items: the seller's taxpayer identification number, the name of the selling unit, the selling unit's telephone number, the selling unit's address, the invoice issuer, the payee, and the reviewer.

25. The payment and invoicing linkage system according to claim 15, characterized in that: The pre-invoicing information includes a merchant number and product information, wherein the product information includes product name, tax code, and tax rate.

26. The payment and invoicing linkage system according to claim 15, characterized in that: The payment information includes payment amount, payment method, payment time, and payment account information.

27. The payment and invoicing linkage system according to claim 15, characterized in that: The execution of the computer program also results in the following operations: Receive the invoicing result from the invoicing agency and save the invoice data; In the case where the transaction terminal is a user payment terminal, returning the invoicing result to the transaction terminal; In the case where the transaction terminal is a merchant payment terminal, the invoicing result is returned to the user's payment application.

28. The payment and invoicing linkage system according to claim 27, characterized in that: The execution of the computer program also results in the following operations: With the user's authorization, the invoice data and signature verification results will be sent to the reimbursement system or a third-party reimbursement platform.

29. An automatic invoicing method, characterized in that: The method is applied to a merchant system including a merchant backend subsystem and a merchant code display terminal, and the method includes the following steps: The merchant backend subsystem sends an activation request to the payment and invoicing linkage system, wherein the activation request includes the merchant's merchant number and the seller's invoicing information; The merchant backend subsystem sends pre-invoicing information to the payment and invoicing linkage system; The merchant backend subsystem receives the payment invoicing linkage code returned by the payment invoicing linkage system, wherein the payment invoicing linkage code is associated with the merchant's sales party invoicing information and the pre-invoicing information; and The merchant's code display terminal presents the payment invoicing linkage code in a scannable manner for the user to scan and pay.

30. A merchant system, characterized in that: The merchant system includes a merchant backend subsystem and a merchant code display terminal, wherein: The merchant backend subsystem is configured as follows: Sending an activation request to the payment and invoicing linkage system, wherein the activation request includes the merchant's merchant number and the seller's invoicing information; Sending pre-invoicing information to the payment and invoicing linkage system; receiving a payment invoicing linkage code returned by the payment invoicing linkage system, wherein the payment invoicing linkage code is associated with the seller invoicing information of the merchant and the pre-invoicing information; and The merchant code display terminal is configured as follows: The payment invoicing linkage code is presented in a scannable manner so that the user can scan the code to pay.

31. An automatic invoicing method, characterized in that: The method is applied to a merchant system including a merchant backend subsystem and a merchant payment terminal, and the method comprises the following steps: The merchant backend subsystem sends an activation request to the payment and invoicing linkage system, wherein the activation request includes the merchant's merchant number and the seller's invoicing information; The merchant backend subsystem sends pre-invoicing information to the payment and invoicing linkage system; The merchant backend subsystem receives the pre-invoicing identifier returned by the payment invoicing linkage system, wherein the pre-invoicing identifier is associated with the merchant's sales party invoicing information and the pre-invoicing information; The merchant payment terminal generates payment information in response to the user's payment behavior; and The merchant payment terminal assembles the payment information and the pre-invoicing identifier into a payment request, and sends the payment request to the payment and invoicing linkage system.

32. A merchant system, characterized in that: The merchant system includes a merchant backend subsystem and a merchant payment terminal, wherein: The merchant backend subsystem is configured as follows: Sending an activation request to the payment and invoicing linkage system, wherein the activation request includes the merchant's merchant number and the seller's invoicing information; Sending pre-invoicing information to the payment and invoicing linkage system; receiving a pre-invoicing identifier returned by the payment and invoicing linkage system, wherein the pre-invoicing identifier is associated with the seller's invoicing information of the merchant and the pre-invoicing information; and The merchant payment terminal is configured as follows: generating payment information in response to a user payment action; The payment information and the pre-invoicing identifier are assembled into a payment request, and the payment request is sent to the payment and invoicing linkage system.

33. An automatic invoicing method, characterized in that: The method is applied to a user terminal, and the method comprises the following steps: Receive the payment result and the ID of the order to be invoiced sent by the payment and invoicing linkage system; Presenting the payment result to the user; In response to a user invoicing instruction, assembling the purchaser invoicing information input by the user and the to-be-invoiced order identifier into a user invoicing request, and sending the user invoicing request to the payment and invoicing linkage system; and Receive the billing result returned by the payment and billing linkage system.

34. The automatic invoicing method according to claim 33, characterized in that: The method further comprises: Identifying a payment invoicing linkage code generated by the payment invoicing linkage system, wherein the payment invoicing linkage code carries a pre-invoicing identifier, and the pre-invoicing identifier is associated with the merchant's sales party invoicing information and pre-invoicing information; and In response to the user's payment behavior, a payment request is sent to the payment and invoicing linkage system, wherein the payment request includes payment information and the pre-invoicing identifier.

35. A user terminal, characterized in that: The user terminal is configured as follows: Receive the payment result and the ID of the order to be invoiced sent by the payment and invoicing linkage system; Presenting the payment result to the user; In response to a user invoicing instruction, assembling the purchaser invoicing information input by the user and the to-be-invoiced order identifier into a user invoicing request, and sending the user invoicing request to the payment and invoicing linkage system; as well as Receive the billing result returned by the payment and billing linkage system.

36. The user terminal according to claim 33, characterized in that: The user terminal is configured as follows: Identifying a payment invoicing linkage code generated by the payment invoicing linkage system, wherein the payment invoicing linkage code carries a pre-invoicing identifier, and the pre-invoicing identifier is associated with the merchant's sales party invoicing information and pre-invoicing information; and In response to the user's payment behavior, a payment request is sent to the payment and invoicing linkage system, wherein the payment request includes payment information and the pre-invoicing identifier.

37. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes instructions, which, when executed, execute the automatic invoicing method according to any one of claims 1-14, 29, 31, 33-34.

38. A computer program product, characterized in that It comprises a computer program, which, when executed by a processor, implements the automatic invoicing method according to any one of claims 1-14, 29, 31, 33-34.

Images