CN110264214B

CN110264214B - Transaction bill generation and verification method, device and equipment

Info

Publication number: CN110264214B
Application number: CN201910448609.8A
Authority: CN
Inventors: 田野
Original assignee: Advanced New Technologies Co Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2019-05-28
Filing date: 2019-05-28
Publication date: 2024-02-13
Anticipated expiration: 2039-05-28
Also published as: CN110264214A

Abstract

The embodiment of the specification discloses a method, a device and equipment for generating and verifying transaction bills. The scheme comprises the following steps: acquiring transaction sub-account information of a collection flow, wherein the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts; determining transaction information corresponding to the collection running water according to the transaction sub-account information, wherein the transaction sub-account information corresponds to the transaction information one by one, and the transaction information comprises user information and product information; generating a receipt according to the transaction information; and verifying the transaction bill according to the receipt.

Description

Transaction bill generation and verification method, device and equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for generating and verifying a transaction bill.

Background

In the prior art, in the traditional business, the number of clients corresponding to a company is limited, hundreds of small clients and tens of thousands of large clients, and meanwhile, fund receipt and payment occur infrequently, and the whole workload can be manually completed through a plurality of financial clients and urine clients. In the internet background of today, a large number of science and technology companies face small and medium-sized merchants, the number of target customer groups reaches millions or even tens of millions, and accounts receivable are produced in a trade every moment. At this time, the mass collection confirmation, bill verification and verification cannot be achieved through manpower, and the system must be relied on to automatically identify the collection and verify the bill. However, in this case, one bank card account is faced with millions of cash flows every day, and the system cannot confirm which transaction bill corresponds to each payment, and a lot of screening work is required, which is time-consuming and laborious, so that bill verification cannot be performed efficiently.

Disclosure of Invention

In view of this, the embodiments of the present application provide a method, apparatus, and device for generating and verifying a transaction bill, which are used for improving verification efficiency of the transaction bill.

In order to solve the above technical problems, the embodiments of the present specification are implemented as follows:

the embodiment of the specification provides a transaction bill verification method, which comprises the following steps:

acquiring transaction sub-account information of a collection flow, wherein the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts;

determining transaction information corresponding to the collection running water according to the transaction sub-account information, wherein the transaction sub-account information corresponds to the transaction information one by one, and the transaction information comprises user information and product information;

generating a receipt according to the transaction information;

and verifying the transaction bill according to the receipt.

The method for generating the transaction bill provided by the embodiment of the specification comprises the following steps:

the method comprises the steps that transaction information is obtained, the transaction information comprises user information and product information, the transaction information corresponds to transaction sub-account information one by one, the transaction sub-accounts are generated by a third party system according to entity transaction accounts, and one entity transaction account corresponds to a plurality of transaction sub-accounts;

And generating a transaction bill according to the transaction information.

The embodiment of the specification provides a transaction bill verifying and verifying device, which comprises:

the transaction sub-account information determining module is used for obtaining transaction sub-account information of a collection flow, wherein the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts;

the transaction information determining module is used for determining transaction information corresponding to the collection running water according to the transaction sub-account information, the transaction sub-account information corresponds to the transaction information one by one, and the transaction information comprises user information and product information;

the receipt generation module is used for generating a receipt according to the transaction information;

and the transaction bill verification module is used for verifying and verifying the transaction bill according to the receipt.

The device for generating transaction bill provided in the embodiment of the present specification includes:

the transaction information acquisition module is used for acquiring transaction information, wherein the transaction information comprises user information and product information, the transaction information corresponds to the transaction sub-account information one by one, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts;

And the transaction bill generation module is used for generating a transaction bill according to the transaction information.

The embodiment of the specification provides a transaction bill verification device, which comprises:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

generating a receipt according to the transaction information;

and verifying the transaction bill according to the receipt.

The embodiment of the specification provides a transaction bill generation device, which comprises:

at least one processor; the method comprises the steps of,

A memory communicatively coupled to the at least one processor; wherein,

and generating a transaction bill according to the transaction information.

The above-mentioned at least one technical scheme that this description embodiment adopted can reach following beneficial effect:

according to the embodiment of the specification, the transaction information formed by the user information and the product information is taken as a whole, and a unique transaction sub-account is allocated for different transaction information, so that which transaction information is can be determined according to the collection account of the collection flow, after the collection bill is generated, the transaction bill comprising the transaction information can be verified, the problem that massive flows cannot be effectively identified is effectively solved, and verification efficiency of the transaction bill is greatly improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

fig. 1 is a flow chart of a method for generating a transaction bill according to an embodiment of the present disclosure;

FIG. 2 is a schematic flow chart of a method for verifying and verifying a transaction bill according to an embodiment of the present disclosure;

FIG. 3 is a flow chart of another method for verifying and verifying a transaction bill according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of a transaction bill generating device corresponding to FIG. 1 according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural view of a verification device corresponding to the transaction bill of FIG. 2 according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a transaction bill generating device corresponding to FIG. 1 according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a verification device corresponding to the transaction bill of fig. 2 according to an embodiment of the present disclosure.

Detailed Description

For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In the traditional enterprise operation, a business transaction flow is as follows:

1. the company A and the company B sign business contracts, and determine goods service, money, period, delivery mode and the like;

2. a completes goods or services, delivers to B, and generates accounts receivable at the moment;

3. b, confirming goods or services, and finishing checking with the A;

4. a, invoicing to B, and B paying to an A bank account to inform A that the money is paid;

5. and (3) the bank account A receives the funds, and after confirming that the funds are paid for B, the accounts receivable are checked and approved.

In traditional business, the number of clients corresponding to a company is limited (hundreds of small, tens of thousands of large), and funds receipt and payment occur infrequently, and the whole workload can be completed manually through a plurality of financial peeks. In the internet background of today, a large number of science and technology companies face small and medium merchants, the number of target customer groups reaches millions or even tens of millions, and accounts receivable is produced in a trade at any moment. At this time, the mass collection confirmation, bill verification and verification cannot be achieved through manpower, and the system must be relied on to automatically identify the collection and verify the bill. In this case, the following problems occur:

1. one bank card faces millions of cash flows every day, and the system cannot confirm each cash making merchant;

2. One company can push out a plurality of products and services, the same merchant can sign up different services, and the payment of the different services of the same merchant cannot be automatically identified.

The embodiment of the specification discards the identification scheme based on the merchant name, and focuses on locking the unique association relationship between the collection account and the user and the product in the signing link, so that a unique account is distributed for the user and the product, mutual isolation is realized, the conflict is avoided, and the problem of mass flow identification of a single account is fundamentally solved.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 is a flow chart of a method for generating a transaction bill according to an embodiment of the present disclosure. From the program perspective, the execution subject of the flow may be a program or an application client that is installed on an application server.

As shown in fig. 1, the process may include the steps of:

s101: the method comprises the steps of obtaining transaction information, wherein the transaction information comprises user information and product information, the transaction information corresponds to transaction sub-account information one by one, the transaction sub-accounts are generated by a third party system according to entity transaction accounts, and one entity transaction account corresponds to a plurality of transaction sub-accounts.

In the embodiment of the present disclosure, the transaction information may be obtained from a system of the user, or may be obtained from a third party system, or may be obtained automatically by setting rules, or may be manually input, which is not limited herein.

In the present embodiment, the transaction information may include various information such as user information and product information. The user referred to herein may be a user of the product, i.e. a party who receives a service or commodity, who needs to have the provider of the service or product pay for the account. The user can be a merchant of the internet shopping platform or a buyer of the product in the internet shopping platform. When the user is a merchant, the execution subject of the method is a billing system of an internet shopping platform. When the user is a buyer, the execution subject of the method is a billing system of a merchant of the internet shopping platform.

In the embodiment of the present specification, the product information may be a service or a commodity. The services may be business promotion services, store decoration services, account balance promotion services, etc. provided by the internet shopping platform for merchants. The commodity may be an item purchased by a purchaser, such as a household appliance, clothing, or cosmetic product.

In the embodiment of the present disclosure, the transaction sub-account is generated by the third party system according to an entity transaction account, where one entity transaction account corresponds to a plurality of transaction sub-accounts. The third party system can be a banking system and also can be an account system provided by an internet shopping platform. The transaction sub-account is a sub-account of the entity transaction account, and the transaction sub-account is consistent with the function of the entity transaction account and shares funds. The physical transaction account is a collection account and the transaction sub-account may also be used to collect accounts.

In the embodiment of the present disclosure, the transaction information corresponds to the transaction sub-accounts one by one, that is, if the collecting account of a transaction is known as a transaction sub-account, what the transaction information is can be determined according to the transaction sub-account, and a transaction bill can be verified.

S102: and generating a transaction bill according to the transaction information.

In the embodiment of the present disclosure, a transaction bill is generated according to transaction information, where the transaction bill includes at least transaction information, and may further include other information such as an amount of money. The transaction bill is the bill of accounts receivable.

The method in fig. 1 is to assign a unique transaction sub-account to different transaction information by taking the transaction information composed of the user information and the product information as a whole, and generate a transaction bill according to the transaction information. According to the embodiment of the specification, the unique association relation between the collection account and the user and the product is locked, so that the unique account is allocated to the user and the product, the unique account is isolated from each other, the conflict is avoided, the problem of mass flow identification of the single account is fundamentally solved, and the verification and marketing efficiency of the transaction bill is greatly improved.

Based on the method of fig. 1, the examples of the present specification also provide some specific implementations of the method, as described below.

In the prior art, for a provider, it is generally fixed in existence as an entity account of the collection account. The transaction information of the application corresponds to a transaction sub-account, and the transaction sub-account is generated for an entity account and does not exist. Therefore, the existing distribution method of the collection account cannot meet the distribution requirement of the transaction sub-account in the embodiment of the application.

Optionally, in step 102: before generating the transaction bill according to the transaction information, the method may further include:

aiming at an entity bank account, sending an acquisition request of a virtual sub-account to a bank system;

and acquiring a virtual sub-account of the banking system for the entity banking account, wherein the entity banking account comprises a plurality of virtual sub-accounts.

In the embodiment of the present disclosure, when the third party system is a banking system, a transaction sub-account needs to be allocated to the transaction information after the transaction information is acquired. If the transaction information is first generated, an acquisition request needs to be sent to the banking system for acquiring the transaction sub-account. The transaction sub-account must correspond to an entity bank account, and therefore, when the acquisition request is sent, an entity bank account must be designated.

In the embodiment of the present disclosure, in response to the acquiring request, the banking system may add a virtual sub-account for the physical banking account, and then may feed back the virtual sub-account to the request sending system. The system sending system can be a login system of an entity bank account, and can also be a third party system corresponding to the bank system, such as a billing system. The virtual sub-account may be embodied by adding a serial number to the physical account, for example, (5719 x 001-002019), 5719 x 001 is the physical account, and 002019 is the serial number. 2019 sub-account representing entity account 5719 x 001.

In this embodiment of the present disclosure, after the request sending system obtains the virtual sub-account, the virtual sub-account is in one-to-one correspondence with the transaction information.

In this embodiment of the present description, the banking system defaults to one physical bank account including multiple virtual sub-accounts, the number of which is on the order of millions. When the request exceeds this number, further virtual sub-accounts may be applied to the banking system.

In the prior art, when the information of the transaction bill is filled, a method of manually filling is often adopted, and the method is time-consuming and labor-consuming and is easy to cause errors.

Optionally, the acquiring transaction information may specifically include:

acquiring a contract submitted by a user;

and determining transaction information according to the contract.

Various methods for acquiring transaction information are provided, and in order to improve efficiency, an embodiment of the present disclosure provides a method for automatically acquiring transaction information.

In the embodiment of the present specification, the contract is a contract made by a user with a product provider, both parties contract fulfilling both obligations according to terms of the contract. The contract explicitly records information of the user and the product provider, can also prescribe the types, the quantity, the unit price and the like of products required to be provided by the product provider, and can also comprise the time limit for providing the delivery of the products. The contract may also define the payment actions of the user, such as what rules the user pays after receiving the service or product. If the product is paid within a set time range after being received, the payment can be monthly, quarterly, annual and the like.

When the user is a merchant of the internet shopping platform, before entering a shopping platform or using each service, the user has a service notice for the merchant to read, the service notice has introduction of the product and other relevant information, and if the merchant has no doubt, the user clicks and agrees, so that a subscription contract is generated.

When the user is a buyer of the shopping platform, after the user selects the commodity and places an order, the commodity corresponds to a contract, and related information of the commodity, commodity delivery information and the like are described in detail above.

In the embodiment of the present disclosure, after the contract submitted by the user is obtained, the required information, such as the user information and the product information, may be obtained from the contract, so that the transaction information may be obtained.

Optionally, the method further comprises:

and sending the transaction sub-account corresponding to the transaction information to the user, and reminding the user to pay money to the transaction sub-account.

In the embodiment of the specification, after the transaction sub-account corresponding to the transaction information is acquired, besides the information of the transaction sub-account is required to be recorded, the transaction sub-account information is required to be sent to the user, so that the user can conveniently pay money to the transaction sub-account, the transaction information is determined according to the collection account, and bill verification is convenient.

In this embodiment of the present disclosure, for the transaction sub-account information, a method of separately sending the transaction sub-account information to the user may be adopted, for example, the transaction sub-account information is displayed in a message column of the merchant in a manner of information pushing, and at this time, it is required to mark which transaction corresponds to. The user may also be notified by adding transaction sub-account information to the sign-up contract as collection account information. And the user pays money according to the information of the collection account on the contract.

Since different users may purchase the same commodity or service multiple times, the transaction information for multiple transaction bills is often the same, such as for monthly services, and the transaction information for different months of transaction bills is the same. In this case, if different transaction sub-accounts are allocated to the same transaction information, the number of transaction sub-accounts is excessive, and resources are wasted.

In view of the above, in an embodiment of the present specification, after the acquiring the transaction information, the method further includes:

judging whether the transaction information exists in the mapping relation library or not, and obtaining a judging result;

when the judgment result indicates that the transaction information exists in the mapping relation library, obtaining a mapping object of the transaction information;

and determining the mapping object as a transaction sub-account corresponding to the transaction bill.

In the embodiment of the present disclosure, if transaction information of a transaction bill appears, transaction sub-account information that has been matched with the transaction information needs to be allocated to the transaction bill when the transaction sub-bill is allocated to the transaction bill.

In order to achieve the above objective, the embodiments of the present disclosure may first create a mapping relation library, where two parties of the mapping relation library are transaction information and transaction sub-accounts, respectively. After the transaction information is acquired, firstly judging whether the transaction information exists in the mapping relation library, and if so, indicating that the transaction information is distributed to the transaction sub-account. Then the sub-account information of the transaction corresponding to the transaction information is extracted from the mapping relation library and is distributed to the transaction bill containing the transaction information.

Optionally, the method may further include:

when the judgment result indicates that the transaction information does not exist in the mapping relation library, sending a sub-account acquisition request to a third party system aiming at an entity account;

sub-account information of the entity account sent by the third party system is obtained;

and determining the sub-account information as a transaction sub-account of the transaction bill.

In the embodiment of the present disclosure, when the transaction information does not exist in the mapping relation library, it is proved that the transaction information appears for the first time, and no transaction sub-account has been allocated yet. At this time, a sub-account needs to be applied to the third party system, and then the sub-account information is determined as the transaction sub-account of the transaction bill.

Optionally, after the determining the sub-account information as the transaction sub-account of the transaction bill, the method further includes:

and storing the corresponding relation between the transaction sub-account and the transaction information into the mapping relation library.

In the embodiment of the specification, after the transaction sub-account is allocated for the transaction information appearing for the first time, the corresponding relation between the transaction information and the transaction sub-account needs to be stored, so that after the transaction information appears again, the transaction sub-account matched with the transaction information is called again, the number of the transaction sub-accounts is reduced, and account resources are saved.

Fig. 2 is a flow chart of a method for verifying and verifying a transaction bill according to an embodiment of the present disclosure. From the program perspective, the execution subject of the flow may be a program or an application client that is installed on an application server.

As shown in fig. 2, the process may include the steps of:

s201: and acquiring transaction sub-account information of a collection flow, wherein the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts.

In the embodiment of the present disclosure, one collection flow corresponds to one collection account, and the transaction sub-account is the collection account. In the embodiment of the present disclosure, the transaction sub-account is generated by the third party system according to an entity transaction account, where one entity transaction account corresponds to a plurality of transaction sub-accounts. The third party system can be a banking system and also can be an account system provided by an internet shopping platform. The transaction sub-account may be a sub-account of an entity transaction account, the transaction sub-account being functionally consistent with the entity transaction account, and the funds being shared. The physical transaction account is a collection account and the transaction sub-account may also be used to collect accounts.

It should be noted that when the transaction sub-account is adopted for collection, the entity account can be set to refuse to receive funds, only the transaction sub-account can receive funds, and erroneous payment is avoided.

S202: and determining transaction information corresponding to the collection running water according to the transaction sub-account information, wherein the transaction sub-account information corresponds to the transaction information one by one, and the transaction information comprises user information and product information.

In the embodiment of the present disclosure, the transaction sub-account information corresponds to the transaction information one by one, and the transaction information corresponding to the collection flow can be determined according to the transaction sub-account. The correspondence between the transaction sub-account and the transaction sub-bill may be stored in advance, and the storage manner is not particularly limited.

In the present description embodiment, the transaction information may include user information and product information. The user may be a user of the product, i.e. a party who receives a service or commodity, needs to have the provider of the service or product pay for the account. The user can be a merchant of an internet shopping platform or a buyer of internet shopping.

S203: and generating a receipt according to the transaction information.

In the embodiment of the present specification, after the transaction information is acquired, a receipt may be generated. The bill is a business act of collecting goods deposit or pre-collection, and the bill can process the business of enterprise sales collection, sales pre-collection and the like

S204: and verifying the transaction bill according to the receipt.

Accounting of accounts receivable may be performed in multiple passes after a single accounts receivable occurs, so that the accounting operator must have a process of accounting for each accounts receivable to prevent fool and bad account.

In the embodiment of the present disclosure, the bill may be used to cancel one transaction bill, or cancel a plurality of transaction bills.

In the method in fig. 2, by taking the transaction information formed by the user information and the product information as a whole, a unique transaction sub-account is allocated for different transaction information, so that which transaction information is can be determined according to the collection account of the collection flow, and after the collection bill is generated, the transaction bill comprising the transaction information can be checked out, thereby effectively solving the problem that massive flows cannot be effectively identified, and greatly improving the checking and selling efficiency of the transaction bill.

Optionally, the determining the transaction information corresponding to the collection running water according to the transaction sub-account information specifically includes:

obtaining a mapping object corresponding to the transaction sub-account from a mapping relation library;

and determining the mapping object as transaction information corresponding to the collection flowing water.

In the embodiment of the present disclosure, a mapping relation library is preset and stored in the system, where both sides of the mapping relation library are transaction information and transaction sub-account information respectively. After the transaction sub-account information is acquired, searching the position stored by the transaction sub-account in the mapping relation library, and after the position where the transaction sub-account exists is determined, the transaction information corresponding to the transaction sub-account can be called. The transaction information is the transaction information of the collection flow.

Optionally, the verifying the transaction bill according to the bill, specifically includes:

judging whether the transaction bill aiming at the transaction information is one or not, and obtaining a judging result;

and when the judging result shows that the transaction bill aiming at the transaction information is one, verifying and canceling the transaction bill by adopting the receipt.

In this embodiment of the present disclosure, when a bill is used to cancel a transaction bill, the transaction information of the bill is determined, and then the transaction bill needs to be screened, so as to screen the transaction bill corresponding to the transaction information. If the transaction corresponding to the transaction information is only performed once, only one transaction bill is generated, and the transaction bill can be directly checked out according to the bill of the transaction information.

In the embodiment of the present disclosure, if the transaction corresponding to the transaction information is only performed once, only one transaction bill is generated, and the transaction bill can be directly checked out according to the bill of the transaction information. However, in some cases, the eligible transaction bill is often not one, and then additional conditions need to be added to complete the verification of the transaction bill.

Optionally, the method further comprises:

acquiring the collection amount of the collection flow;

the generation of the receipt according to the transaction information specifically includes:

and generating a receipt according to the transaction information and the receipt amount.

In order to achieve the above effect, in the embodiment of the present disclosure, the bill for collection includes the amount of collection in addition to the transaction information including the user information and the product information, and the amount of collection may be directly obtained from the collection line. And then generating a receipt according to the transaction information and the receipt amount, so as to complete the verification and the sale of the transaction bill according to the receipt.

Optionally, the method further comprises:

when the judging result shows that the transaction bills aiming at the transaction information are multiple, screening a first transaction bill, wherein the transaction amount of the first transaction bill is the same as the collection amount of the collection flow;

And verifying the first transaction bill by adopting the receipt.

In the embodiment of the present disclosure, when a plurality of transaction bills corresponding to transaction information in a bill are provided, the second filtering may be performed according to the amount of money to be collected. If the first transaction bill with the same transaction amount as the collection amount exists in the transaction bills, the collection bill corresponds to the first transaction bill. The bill for the first transaction may be directly used to cancel the bill for the first transaction.

Optionally, when the first transaction bill is plural, the verifying the first transaction bill by using the bill comprises:

and respectively verifying and verifying the plurality of first transaction bills by adopting the receipt according to the sequence of the generation time of the first transaction bills.

In the embodiment of the present description, for example, the user uses a long-term service, and the payment is made by a monthly payment method, but it is agreed that payment is made within a period of time after receiving the service, for example, 3 months. Then there will be at least 3 transaction bills for that service during the 3 months. Since the transaction amount of each transaction bill is the same as the collection amount of the collection bill, the transaction bill with the earliest generation time can be screened at the moment for better transaction bill verification. And adopting the bill to cancel the transaction bill.

Optionally, the method further comprises:

when the judgment result shows that the transaction bills aiming at the transaction information are multiple, respectively verifying and selling the transaction amounts of the transaction bills by adopting the receipt, and updating the receipt amount of the receipt until the receipt amount of the receipt is zero.

In the embodiment of the present specification, if the user pays for the received product, a specific time is accumulated for payment together. For example, a transaction bill is generated monthly, but paid quarterly, or paid yearly. For this case, since the transaction information of all the transaction bills is the same as the receipt, the transaction bills can be sequentially checked out using the receipt. Each time a transaction bill is approved, the amount of money in the bill is modified accordingly until the amount of money is zero.

Fig. 3 is a flow chart of another method for verifying and verifying a transaction bill according to an embodiment of the present disclosure, and the third party platform of fig. 3 is a banking system. As shown in fig. 3, the method comprises the following steps:

in the signing link, a sub-account number is automatically allocated to each user and product (transaction information), and each user and product is ensured to be uniquely corresponding to the sub-account number. Triggering and calling a new virtual sub-account of the bank, wherein the real account is 5719 x 001, and the new sub-account of the bank is 002019, and the information of the collection account is (5719 x 001-002019). If a single entity user supports millions of virtual sub-accounts, multiple entity sub-accounts may be applied if the threshold is exceeded.

After signing, pushing merchant collection information to an entity account and sub-account format, for example (5719 x 001-002019).

When a transaction reconciliation occurs, the merchant pays to the sub-account (5719 x 001-002019).

The system pulls all the collection flowing water of the sub account (5719, 001-002019), and the corresponding user + product of the collection is topped according to the sub account information.

And creating a corresponding bill for the bill collection flow, and verifying the corresponding transaction bill.

The embodiment of the specification discards the identification scheme based on the merchant name, and focuses on locking the unique association relationship between the collection account and the user and the product in the signing link, so that a unique account is distributed for the user and the product, the unique account is isolated from each other, the conflict is avoided, and the problem of mass flow identification of a single account is fundamentally solved.

Based on the same thought, the embodiment of the specification also provides a device corresponding to the transaction bill generation method. Fig. 4 is a schematic structural diagram of a device for generating a transaction bill corresponding to fig. 1 according to an embodiment of the present disclosure. As shown in fig. 4, the apparatus may include:

a transaction information obtaining module 401, configured to obtain transaction information, where the transaction information includes user information and product information, the transaction information corresponds to the transaction sub-account information one by one, and the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts;

And the transaction bill generating module 402 is configured to generate a transaction bill according to the transaction information.

The apparatus of fig. 4 generates a transaction bill based on transaction information by assigning a unique transaction sub-account to different transaction information by taking the transaction information composed of user information and product information as a whole. According to the embodiment of the specification, the unique association relation between the collection account and the user and the product is locked, so that the unique account is allocated to the user and the product, the unique account is isolated from each other, the conflict is avoided, the problem of mass flow identification of the single account is fundamentally solved, and the verification and marketing efficiency of the transaction bill is greatly improved.

Optionally, the apparatus may further include:

the first acquisition request sending module is used for sending an acquisition request of the virtual sub-account to the bank system aiming at the entity bank account;

the virtual sub-account acquisition module is used for acquiring a virtual sub-account of the banking system aiming at the entity banking account, wherein the entity banking account comprises a plurality of virtual sub-accounts.

Optionally, the transaction information obtaining module 401 may specifically include:

the contract signing acquisition unit is used for acquiring contract signing submitted by the user;

and the transaction information determining unit is used for determining transaction information according to the contract.

Optionally, the apparatus may further include:

and the transaction sub-account sending module is used for sending the transaction sub-account corresponding to the transaction information to the user and reminding the user to pay money to the transaction sub-account.

Optionally, after the acquiring the transaction information, the apparatus may further include:

the second result judging module is used for judging whether the transaction information exists in the mapping relation library or not, and obtaining a judging result;

the mapping object obtaining module is used for obtaining a mapping object of the transaction information when the judgment result indicates that the transaction information exists in the mapping relation library;

and the transaction sub-account determining module is used for determining the mapping object as the transaction sub-account corresponding to the transaction bill.

Optionally, the apparatus may further include:

the second acquisition request sending module is used for sending an acquisition request of a sub-account to a third party system aiming at an entity account when the judgment result indicates that the transaction information does not exist in the mapping relation library;

the sub-account information acquisition module is used for acquiring sub-account information of the entity account sent by the third party system;

And the transaction sub-account determining module is used for determining the sub-account information as a transaction sub-account of the transaction bill.

Optionally, the apparatus may further include:

and the storage module is used for storing the corresponding relation between the transaction sub-account and the transaction information into the mapping relation library after the sub-account information is determined to be the transaction sub-account of the transaction bill.

Based on the same thought, the embodiment of the specification also provides a corresponding device of the transaction bill verification method. Fig. 5 is a schematic structural diagram of a verification device corresponding to the transaction bill of fig. 2 according to an embodiment of the present disclosure. As shown in fig. 5, the apparatus may include:

the transaction sub-account information determining module 501 is configured to obtain transaction sub-account information of a collection flow, where the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts;

the transaction information determining module 502 is configured to determine transaction information corresponding to the collection running water according to the transaction sub-account information, where the transaction sub-account information corresponds to the transaction information one by one, and the transaction information includes user information and product information;

A bill generation module 503, configured to generate a bill according to the transaction information;

and the transaction bill verification module 504 is configured to verify the transaction bill according to the receipt.

The device in fig. 5 takes the transaction information formed by the user information and the product information as a whole, and distributes a unique transaction sub-account for different transaction information, so that the transaction information can be determined according to the collection account of collection flow, and after the collection bill is generated, the transaction bill comprising the transaction information can be checked out, thereby effectively solving the problem that massive flow cannot be effectively identified, and greatly improving the checking and selling efficiency of the transaction bill.

Optionally, the transaction information determining module 502 may specifically include:

the mapping object acquisition unit is used for acquiring the mapping object corresponding to the transaction sub-account from the mapping relation library;

and the transaction information determining unit is used for determining the mapping object as transaction information corresponding to the collection running water.

Optionally, the apparatus may further include:

the collection amount acquisition module is used for acquiring the collection amount of the collection flow;

the bill generation module 503 is specifically configured to generate a bill according to the transaction information and the amount of money.

Optionally, the transaction bill verification module 504 may specifically include:

the result judging unit is used for judging whether the transaction bill aiming at the transaction information is one or not, and obtaining a judging result;

and the first verifying and verifying unit is used for verifying and verifying the transaction bill by adopting the receipt when the judging result shows that the transaction bill aiming at the transaction information is one.

Optionally, the transaction bill verification module 504 may further include:

a first transaction bill screening unit, configured to screen a first transaction bill when the determination result indicates that the transaction bill for the transaction information is plural, where a transaction amount of the first transaction bill is the same as a collection amount of the collection line;

and the second verifying and verifying unit is used for verifying and verifying the first transaction bill by adopting the receipt.

Optionally, the second verifying and verifying unit is specifically configured to verify, when the first transaction bill is multiple, the multiple first transaction bills by using the receipt according to the sequence of the generation time of the first transaction bill.

Optionally, the transaction bill verification module 504 further includes:

and the third verifying and verifying unit is used for verifying and verifying the transaction amounts of the transaction bills by adopting the receipt when the judging result shows that the transaction bills aiming at the transaction information are multiple, and updating the receipt of the receipt until the receipt of the receipt is zero.

Based on the same thought, the embodiment of the specification also provides equipment corresponding to the transaction bill generation method.

Fig. 6 is a schematic structural diagram of a transaction bill generating device corresponding to fig. 1 according to an embodiment of the present disclosure. As shown in fig. 6, the apparatus 600 may include:

at least one processor 610; the method comprises the steps of,

a memory 630 communicatively coupled to the at least one processor; wherein,

the memory 630 stores instructions 620 executable by the at least one processor 610 to enable the at least one processor 610 to:

and generating a transaction bill according to the transaction information.

The apparatus of fig. 6 generates a transaction bill based on transaction information by assigning a unique transaction sub-account to different transaction information by taking the transaction information composed of user information and product information as a whole. According to the embodiment of the specification, the unique association relation between the collection account and the user and the product is locked, so that the unique account is allocated to the user and the product, the unique account is isolated from each other, the conflict is avoided, the problem of mass flow identification of the single account is fundamentally solved, and the verification and marketing efficiency of the transaction bill is greatly improved.

Based on the same thought, the embodiment of the specification also provides equipment corresponding to the transaction bill verification method.

Fig. 7 is a schematic structural diagram of a verification device corresponding to the transaction bill of fig. 2 according to an embodiment of the present disclosure. As shown in fig. 7, the apparatus 700 may include:

at least one processor 710; the method comprises the steps of,

a memory 730 communicatively coupled to the at least one processor; wherein,

the memory 730 stores instructions 720 executable by the at least one processor 710, the instructions being executable by the at least one processor 710 to enable the at least one processor 710 to:

generating a receipt according to the transaction information;

and verifying the transaction bill according to the receipt.

The device in fig. 7 takes the transaction information formed by the user information and the product information as a whole, and distributes a unique transaction sub-account for different transaction information, so that the transaction information can be determined according to the collection account of collection flow, and after the collection bill is generated, the transaction bill comprising the transaction information can be checked out, thereby effectively solving the problem that massive flow cannot be effectively identified, and greatly improving the checking and selling efficiency of the transaction bill.

In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmelAT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A method of verifying and approving a transaction bill, comprising:

acquiring transaction sub-account information of a collection flow, wherein the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts; the transaction sub-account is consistent in function with the entity transaction account and shares funds;

Generating a receipt according to the transaction information;

and verifying the transaction bill according to the receipt.

2. The method as claimed in claim 1, wherein the determining transaction information corresponding to the collection flow according to the transaction sub-account information specifically includes:

3. The method of claim 1, the method further comprising:

acquiring the collection amount of the collection flow;

4. The method as claimed in claim 3, wherein said verifying transaction bill according to said bill comprises:

5. The method of claim 4, the method further comprising:

And verifying the first transaction bill by adopting the receipt.

6. The method of claim 5, wherein when the first transaction bill is plural, the verifying the first transaction bill using the bill of collection specifically comprises:

7. The method of claim 4, the method further comprising:

8. A method of generating a transaction bill, comprising:

the method comprises the steps that transaction information is obtained, the transaction information comprises user information and product information, the transaction information corresponds to transaction sub-account information one by one, the transaction sub-accounts are generated by a third party system according to entity transaction accounts, and one entity transaction account corresponds to a plurality of transaction sub-accounts; the transaction sub-account is consistent in function with the entity transaction account and shares funds;

And generating a transaction bill according to the transaction information.

9. The method of claim 8, further comprising, prior to generating a transaction bill from the transaction information:

10. The method of claim 8, wherein the acquiring transaction information specifically comprises:

acquiring a contract submitted by a user;

and determining transaction information according to the contract.

11. The method of claim 8, the method further comprising:

12. The method of claim 8, after the acquiring transaction information, the method further comprising:

13. The method of claim 12, the method further comprising:

14. The method of claim 12, further comprising, after the determining the sub-account information as a transaction sub-account of the transaction bill:

15. A transaction bill verification device comprising:

the transaction sub-account information determining module is used for obtaining transaction sub-account information of a collection flow, wherein the transaction sub-account is a collection account, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts; the transaction sub-account is consistent in function with the entity transaction account and shares funds;

16. The apparatus of claim 15, the transaction information determination module specifically comprising:

17. A transaction bill generation device, comprising:

the transaction information acquisition module is used for acquiring transaction information, wherein the transaction information comprises user information and product information, the transaction information corresponds to the transaction sub-account information one by one, the transaction sub-account is generated by a third party system according to an entity transaction account, and one entity transaction account corresponds to a plurality of transaction sub-accounts; the transaction sub-account is consistent in function with the entity transaction account and shares funds;

18. The apparatus of claim 17, the apparatus further comprising:

The acquisition request sending module is used for sending an acquisition request of the virtual sub-account to the bank system aiming at the entity bank account;

19. A transaction bill verification apparatus comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

Generating a receipt according to the transaction information;

and verifying the transaction bill according to the receipt.

20. A transaction bill generation device, comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

and generating a transaction bill according to the transaction information.