Revenue data processing methods, devices, equipment and media

Abstract

This invention relates to the field of data processing technology, providing a method, apparatus, device, and medium for processing revenue data. The method includes: when a user is detected engaging in a target business, acquiring the business identifier and transaction activity data corresponding to the target business; using the business identifier to determine the revenue model; performing revenue calculation based on the revenue model according to a revenue calculation strategy to obtain a revenue calculation type; using the revenue calculation type and transaction activity data to perform revenue compatibility processing to obtain a revenue file; and performing revenue display processing on the revenue file. This invention can be applied to fund trading scenarios in the financial field. By implementing embodiments of this invention to perform revenue determination, revenue calculation, and revenue compatibility processing on the business identifier and transaction activity data to obtain a revenue file, the revenue file can be displayed in real time, supporting both natural day and transaction day calculations, and enabling compatible processing of direct sales and agency sales, thereby improving the stability and real-time performance of processing efficiency.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and can be applied to the financial field, particularly to a method, apparatus, equipment, and medium for processing revenue data. Background Technology

[0002] Current financial target business revenue data processing technologies only support revenue calculation on a calendar day basis, suitable for direct sales funds and multiple fund companies. As businesses grow, most companies will integrate with fund distribution companies that use transaction day revenue calculation. However, the calculation benchmarks for calendar day and transaction day revenue data are inconsistent, and current technology cannot process both simultaneously. Furthermore, existing technologies exhibit incompatibility in the display mechanisms for calendar day and transaction day revenue data. For example, when integrating with the distribution model, revenue data updates may experience interruptions or delays, leading to delays in data processing efficiency.

[0003] Therefore, existing revenue data processing technologies only support calendar day accounting and are not compatible with transaction day accounting, resulting in data incompatibility and delays in data processing efficiency. Summary of the Invention

[0004] This invention provides a revenue data processing method, apparatus, device, and medium, aiming to solve the problem that existing revenue data processing technologies only support calendar day accounting and cannot be compatible with transaction day accounting, resulting in data incompatibility and data processing efficiency delays.

[0005] To address the aforementioned problems, in a first aspect, embodiments of the present invention provide a revenue data processing method, the revenue data processing method comprising: When a user is detected to be conducting a target service, the service identifier and transaction data corresponding to the target service are obtained; The revenue model is obtained by using the business identifier to determine the revenue model, which includes a first revenue model, a second revenue model, and a third revenue model. The revenue model is processed according to a preset revenue calculation strategy to obtain a revenue calculation type, which is a first natural day calculation, a second natural day calculation, and a transaction day calculation. A revenue file is obtained by performing revenue compatibility processing using the aforementioned revenue accounting type and the aforementioned transaction activity data; The revenue file is then processed to display the revenue.

[0006] Secondly, embodiments of this application provide a revenue data processing apparatus, the revenue data processing apparatus comprising: The acquisition unit is used to acquire the business identifier and transaction data corresponding to the target business when it is detected that a user has processed the target business; A revenue model determination unit is used to perform revenue model determination processing using the business identifier to obtain a revenue model, wherein the revenue model includes a first revenue model, a second revenue model, and a third revenue model. The revenue calculation unit is used to perform revenue calculation processing on the revenue model according to a preset revenue calculation strategy to obtain the revenue calculation type, wherein the revenue calculation type is the first natural day calculation, the second natural day calculation, and the transaction day calculation. A revenue compatibility unit is used to perform revenue compatibility processing using the revenue accounting type and the transaction activity data to obtain a revenue file; The revenue display unit is used to display the revenue from the revenue file.

[0007] Thirdly, embodiments of this application provide a computer device, the computer device including a memory and a processor connected to the memory; the memory is used to store a computer program, and the processor is used to run the computer program stored in the memory to perform the method described in the first aspect above.

[0008] Fourthly, embodiments of this application provide a storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, implement the method described in the first aspect above.

[0009] This invention provides a revenue data processing method, apparatus, device, and medium. The method includes: when a user is detected engaging in a target business, acquiring a business identifier and transaction activity data corresponding to the target business; using the business identifier to perform revenue model judgment processing to obtain a revenue model; performing revenue calculation processing on the revenue model according to a preset revenue calculation strategy to obtain a revenue calculation type; using the revenue calculation type and the transaction activity data to perform revenue compatibility processing to obtain a revenue file; and performing revenue display processing on the revenue file. Therefore, this invention performs revenue model judgment processing, revenue calculation processing, and revenue compatibility processing on the business identifier and transaction activity data to obtain a revenue model, revenue calculation type, and revenue file. The revenue model includes a first revenue model, a second revenue model, and a third revenue model. The revenue calculation type includes first natural day calculation, second natural day calculation, and transaction day calculation. The revenue model judgment processing and revenue calculation processing closely link the revenue model and revenue calculation type to simultaneously support natural day and transaction day calculations, and the revenue file is displayed to achieve compatibility processing for direct sales and agency sales, thereby improving the stability, real-time performance, and accuracy of processing efficiency. Attached Figure Description

[0010] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 A flowchart illustrating the revenue data processing method provided in an embodiment of the present invention; Figure 2 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 3 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 4 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 5 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 6 A schematic block diagram of a revenue data processing apparatus provided in an embodiment of the present invention; Figure 7 A schematic block diagram of a computer device provided for an embodiment of the present invention. Detailed Implementation

[0012] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0013] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0014] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0015] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0016] It should be noted that if any AI models, software tools, or components not belonging to the applicant appear in the embodiments of this application, they are merely illustrative examples and do not represent actual use. The user personal information involved in the embodiments of this application is obtained by an entity authorized (knowing and consenting) by the relevant parties or fully authorized by all parties through various legal and compliant means. The collection, storage, use, processing, transmission, provision, and disclosure of the information, data, and signals involved all comply with relevant laws and regulations and do not violate public order and good morals.

[0017] Please see Figures 1 to 5 , Figure 1 A flowchart illustrating the revenue data processing method provided in an embodiment of the present invention; Figure 2 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 3 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 4 A schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of a sub-process of the revenue data processing method provided in an embodiment of the present invention. Figure 1 As shown, this embodiment of the invention provides a revenue data processing method, which includes the following steps S110-S150.

[0018] S110. When it is detected that a user has processed a target service, obtain the service identifier and transaction data corresponding to the target service.

[0019] In this embodiment, the application scenario of the present invention can be in the fund trading scenario in the financial field. For example, taking the scenario of a user purchasing a fund from a financial institution as an example, the user's fund trading status can be detected in real time, and when the user is detected to be conducting a target business, the business identifier and transaction data corresponding to the target business can be obtained.

[0020] The target business mainly refers to the business situation of purchasing funds, that is, when purchasing funds, obtaining the business identifier and transaction data of the target business; the business identifier refers to the fund code of the purchased fund, that is, a unique identifier; the transaction data includes the business identifier of the purchased fund, the transaction time, principal, total profit amount, total shares, currency, etc.; for example, a user purchases a fund with a business identifier of 012470, the transaction time is 20260330 13:26, the principal is 10000, the total profit amount is 0, the total shares are 10000, and the currency is RMB.

[0021] As can be seen from the above embodiments, when a user is detected to be handling a target business, the business identifier and transaction data corresponding to the target business are obtained to ensure the accuracy of subsequent processing, thereby ensuring the compatibility of the revenue display.

[0022] S120. The revenue model is obtained by using the business identifier to determine the revenue model.

[0023] In this embodiment, after obtaining the business identifier, the revenue model can be determined by using the business identifier.

[0024] Furthermore, the revenue model determination process using the business identifier to obtain the revenue model includes a first revenue model, a second revenue model, and a third revenue model, comprising: Retrieve the account data corresponding to the business identifier from the preset business database; The account type is obtained by performing type acquisition processing on the account data; If the account type is a direct sales account or a distributor account, then the revenue model is determined to be the first revenue model; If the account type is a direct sales account, then the revenue model is determined to be the second revenue model; If the account type is a reseller account, then the revenue model is determined to be the third revenue model.

[0025] In this embodiment, the preset business database may include multiple fund account tables, each of which includes fields such as fund company account, fund company name, business identifier, and account type. The fund company account is the account of the company to which the fund belongs; the fund company name is the company name of the fund company; the business identifier is the unique identifier of the fund; the account type includes direct sales accounts and agency sales accounts. The transaction links of the direct sales accounts and the agency sales accounts are different. For example, the direct sales link only involves the financial target business platform and Fund Company A, while the agency sales link involves the financial target business platform, Fund Company A, and Fund Company B. At the same time, the important difference between the direct sales accounts and the agency sales accounts lies in the transaction time. The transaction time of the direct sales account is 0:00 on the calendar day, while the transaction time of the agency sales account is 15:00 on the transaction day. For example, assuming that the agency sales account records transactions that occur between 15:00 on Friday afternoon and 15:00 on the following Monday, this transaction is counted on the following Monday transaction day, while the direct sales account records the transaction on the transaction date of the day it occurs.

[0026] The step of retrieving the account data corresponding to the business identifier from the preset business database specifically involves using the business identifier as the first search condition to retrieve the corresponding account data from several fund account tables in the preset business database. The account data refers to the data of the fund company corresponding to the business identifier, including the fund company name, business identifier, account type, etc. The number of account data entries can be one or more; that is, the fund company corresponding to the business identifier can be one or more. This means that a fund or business identifier viewed by a user on the front end may correspond to one or more fund companies on the back end.

[0027] The account type is obtained by performing type acquisition processing on the account data. Specifically, the account type is obtained directly from the retrieved account data. The account type includes direct sales account and agency sales account.

[0028] The revenue model includes a first revenue model, a second revenue model, and a third revenue model.

[0029] If the account type is a direct sales account or a distributor account, then the revenue model is determined to be the first revenue model; specifically, when the account type is a direct sales account or a distributor account, the revenue model is determined to be the first revenue model.

[0030] If the account type is a direct sales account, then the revenue model is determined to be the second revenue model; specifically, when the account type is a direct sales account, the revenue model is determined to be the second revenue model.

[0031] If the account type is a reseller account, then the revenue model is determined to be the third revenue model; specifically, when the account type is a reseller account, the revenue model is determined to be the third revenue model.

[0032] Through the above embodiments, it can be seen that: account data corresponding to the business identifier is obtained from a preset business database; the account data is processed to obtain the account type; if the account type is a direct sales account or a reseller account, the revenue model is determined to be the first revenue model; if the account type is a direct sales account, the revenue model is determined to be the second revenue model; if the account type is a reseller account, the revenue model is determined to be the third revenue model. This process, by obtaining and type-based information from the preset business database and business identifier, determines the account type and performs a judgment process to identify a specific revenue model. Therefore, by clearly defining the specific revenue judgment process, the reliability and stability of the revenue model can be ensured, the accuracy of subsequent processing can be ensured, and the compatibility of revenue display can be guaranteed.

[0033] S130. Perform revenue accounting processing on the revenue model according to the preset revenue accounting strategy to obtain the revenue accounting type.

[0034] In this embodiment, after obtaining the revenue model, the revenue model can be processed according to a preset revenue calculation strategy to obtain the revenue calculation type.

[0035] In one embodiment, such as Figure 2 As shown, the revenue calculation process based on the preset revenue calculation strategy for the revenue model yields a revenue calculation type, which includes first natural day calculation, second natural day calculation, and transaction day calculation, comprising: S131. When the revenue model is the first revenue model, the revenue accounting type is confirmed as the first natural day accounting. S132. When the revenue model is the second revenue model, the revenue accounting type is confirmed as the second natural day accounting. S133. When the revenue model is the third revenue model, the revenue calculation type is confirmed as the transaction day calculation.

[0036] In this embodiment, the revenue calculation type includes calendar day calculation and transaction day calculation. The calendar day calculation refers to calculation based on the calendar day dimension, which refers to calendar dates, including weekends, statutory holidays, and other dates. The transaction day calculation refers to calculation based on the transaction day dimension, which refers to dates other than non-trading days, including weekends, statutory holidays, and other dates.

[0037] When the revenue model is the first revenue model, the revenue accounting type is confirmed as the first natural day accounting. Specifically, after determining that the revenue model is the first revenue model, the revenue accounting type is confirmed as the first natural day accounting.

[0038] When the revenue model is the second revenue model, the revenue accounting type is confirmed as the second natural day accounting. Specifically, after determining that the revenue model is the second revenue model, the revenue accounting type is confirmed as the second natural day accounting.

[0039] When the revenue model is the third revenue model, the revenue calculation type is confirmed as the transaction day calculation. Specifically, after determining that the revenue model is the third revenue model, the revenue calculation type is confirmed as the transaction day calculation.

[0040] As can be seen from the above embodiments, the revenue accounting type is obtained by confirming the revenue accounting using the revenue model. By clearly defining the revenue accounting type, the breakpoints or delays that may occur in revenue updates can be reduced, ensuring the accuracy of subsequent processing and thus guaranteeing the compatibility of revenue display.

[0041] S140. Perform revenue compatibility processing using the revenue accounting type and the transaction activity data to obtain a revenue file.

[0042] In this embodiment, after determining the revenue calculation type and the transaction data, the revenue compatibility processing can be performed using the revenue calculation type and the transaction data to obtain a revenue file.

[0043] In one embodiment, such as Figure 3 As shown, the step of using the revenue accounting type and the transaction activity data to perform revenue compatibility processing to obtain the revenue file includes: S141. When the revenue accounting type is first natural day accounting and the current date is a transaction day, a first transaction calculation is performed based on the transaction activity data and the current date to obtain a first revenue file; when the revenue accounting type is first natural day accounting and the current date is a non-transaction day, a second transaction calculation is performed based on the transaction activity data and the current date to obtain a second revenue file.

[0044] S142. When the revenue accounting type is second natural day accounting, a third revenue file is obtained by performing third transaction calculation processing based on the transaction activity data and the current date. S143. When the revenue calculation type is transaction day calculation and the current date is a transaction day, a fourth revenue file is obtained by performing a fourth transaction calculation based on the transaction activity data and the current date; when the revenue calculation type is transaction day calculation and the current date is a non-transaction day, a fifth revenue file is obtained by performing a fifth transaction calculation based on the transaction activity data and the current date.

[0045] In this embodiment, when the revenue calculation type is the first natural day calculation, it is necessary to obtain the current date and determine whether the current date is a trading day or a non-trading day.

[0046] In one embodiment, such as Figure 4 As shown, when the revenue calculation type is first natural day calculation and the current date is a transaction date, the first revenue file is obtained by performing first transaction calculation processing based on the transaction activity data and the current date, including: S144. If the current date is a transaction day and the previous calendar day is a transaction day, then the previous calendar day is taken as the first revenue attribution date. S145. In the acquired push data, the business identifier in the transaction activity data is used to retrieve and obtain the first revenue data for the first revenue attribution date. S146. The transaction activity data and the first revenue data are combined and calculated to obtain the first revenue file.

[0047] In this embodiment, the pushed data is the business revenue data pushed by the fund company corresponding to the business identifier through the interface; the business revenue data may include user identifier, business identifier, revenue date, current revenue amount, and other data.

[0048] In the acquired push data, the business identifier in the transaction activity data is used to retrieve the first revenue data for the first revenue attribution date. Specifically, in the push data, the first revenue attribution date is used as a second search condition. If the first revenue attribution date is found to be equal to the revenue date, the business revenue data corresponding to the revenue date is included in the first revenue data. If the first revenue attribution date is not found to be equal to the revenue date, a third preset display text is used as the first revenue data. The third preset display text includes the third current revenue and the first revenue attribution date, where the third current revenue is revenue in transit.

[0049] The first revenue file is obtained by merging and calculating the transaction activity data and the first revenue data. Specifically, the total revenue amount in the transaction activity data and the current revenue amount in the first revenue data are added together to obtain the cumulative revenue. The current revenue amount, the cumulative revenue, and the first revenue attribution date are used as the first revenue file.

[0050] In one embodiment, such as Figure 5 As shown, when the revenue calculation type is first natural day calculation and the current date is a transaction date, the first revenue file is obtained by performing first transaction calculation processing based on the transaction activity data and the current date, and further includes: S147. If the current date is a trading day and the previous natural day is a non-trading day, then obtain the number M of non-trading days before the current date, and take the M non-trading days before the current date as the first revenue attribution date in sequence. S148. In the pushed data, the business identifier in the transaction data is used to retrieve and obtain the first revenue data for each first revenue attribution date. S149. The transaction activity data and each of the first revenue data are sequentially merged and calculated to obtain the first revenue file.

[0051] In this embodiment, if the current date is a trading day and the previous natural day is a non-trading day, then the number M of non-trading days before the current date is obtained, and the M non-trading days before the current date are sequentially used as the first revenue attribution dates.

[0052] In the pushed data, the business identifier in the transaction data is used to retrieve the first revenue data for each first revenue attribution date. Specifically, in the pushed data, each first revenue attribution date is used sequentially as a second search condition. If a first revenue attribution date equals the revenue date, the business revenue data corresponding to the revenue date is included in the first revenue data. If no first revenue attribution date equals the revenue date is found, a third preset display text is used as the first revenue data. The third preset display text includes the third current revenue and the first revenue attribution date, where the third current revenue is revenue in transit.

[0053] The first revenue file is obtained by sequentially merging and calculating the transaction activity data and each of the first revenue data. Specifically, the total revenue amount in the transaction activity data and the current revenue amount in each of the first revenue data are added sequentially to obtain the cumulative revenue. The current revenue amount, the cumulative revenue, and the first revenue attribution date are used as the first revenue file.

[0054] Further, when the revenue calculation type is first natural day calculation and the current date is a non-trading day, a first revenue file is obtained by performing a first transaction calculation based on the transaction activity data and the current date. Specifically, if the current date is a non-trading day and the previous natural day is a trading day, the previous natural day is taken as the second revenue attribution date. In the pushed data, the business identifier in the transaction activity data is used to retrieve the second dividend data for the second revenue attribution date. The transaction activity data and the second dividend data are then combined and calculated to obtain the second revenue file. If the current date is a non-trading day and the previous natural day is a non-trading day, a first preset revenue text is taken as the second revenue file. Specifically, when the previous natural day is a non-trading day, fund companies in the agency sales model do not push data, so the second preset revenue text is taken as the fifth revenue file. The first preset revenue text includes a first current revenue and a second revenue attribution date, where the first previous revenue is in transit.

[0055] When the revenue calculation type is the second natural day calculation, a third revenue file is obtained by performing a third transaction calculation based on the transaction activity data and the current date. Specifically, the natural day preceding the current date is taken as the third revenue attribution date. In the pushed data, the business identifier in the transaction activity data is used to retrieve and obtain the third dividend data for the third revenue attribution date. The transaction activity data and the third dividend data are then combined and calculated to obtain the third revenue file.

[0056] When the revenue calculation type is transaction day calculation and the current date is a transaction day, a fourth revenue file is obtained by performing a fourth transaction calculation based on the transaction activity data and the current date. Specifically, if the current date is a transaction day and the previous natural day is a transaction day, the previous natural day is taken as the fourth revenue attribution date. In the pushed data, the business identifier in the transaction activity data is used to retrieve the fourth dividend data for the fourth revenue attribution date. The transaction activity data and the fourth dividend data are then combined and calculated to obtain the fourth revenue file. If the current date is a transaction day and the previous natural day is a non-transaction day, the number N of non-transaction days before the current date is obtained, and the N non-transaction days before the current date are sequentially taken as the fourth revenue attribution dates. In the pushed data, the business identifier in the transaction activity data is used to retrieve the fourth dividend data for each of the fourth revenue attribution dates. The transaction activity data and each of the fourth dividend data are then sequentially combined and calculated to obtain the fourth revenue file.

[0057] Further, when the income calculation type is transaction day calculation and the current date is a non-trading day, a fifth income file is obtained by performing a fifth transaction calculation based on the transaction activity data and the current date. Specifically, if the current date is a non-trading day and the previous natural day is a trading day, the previous natural day is taken as the fifth income attribution date. In the pushed data, the business identifier in the transaction activity data is used to retrieve the fifth dividend data for the fifth income attribution date. The transaction activity data and the fifth dividend data are then combined and calculated to obtain the fifth income file. If the current date is a non-trading day and the previous natural day is a non-trading day, a second preset income text is used as the fifth income file. Specifically, when the previous natural day is a non-trading day, fund companies in the agency sales model do not push data, so the second preset income text is used as the fifth income file. The fifth preset income text includes the second current income and the fifth income attribution date, where the second current income is income in transit.

[0058] As can be seen from the above embodiments, the revenue file is obtained by performing revenue compatibility processing using the revenue accounting type and the transaction activity data. This revenue compatibility processing improves the stability of updates and displays, ensures the accuracy of displays, and thus guarantees the compatibility processing of revenue displays.

[0059] S150. Perform revenue display processing on the revenue file.

[0060] In this embodiment, after the revenue file is determined, the revenue file can be processed for revenue display.

[0061] In one embodiment, the process of displaying revenue in the revenue file includes: The revenue file is then converted to obtain the target revenue data; The target revenue data will be pushed and displayed to the user.

[0062] In this embodiment, the conversion process of the revenue file to obtain target revenue data specifically involves converting the current revenue amount or current income in the revenue file into the target revenue amount, and converting the revenue attribution date in the revenue file into the target revenue date. The target revenue data can be in the format of a data table, etc. The current income includes a first current income, a second current income, and a third current income, etc., and the revenue attribution date includes a first revenue attribution date, a second revenue attribution date, a third revenue attribution date, a fourth revenue attribution date, and a fifth revenue attribution date. The revenue file can include a first revenue file, a second revenue file, a third revenue file, a fourth revenue file, and a fifth revenue file.

[0063] In summary, when a user is detected engaging in a target business, this embodiment of the invention obtains the business identifier and transaction data corresponding to the target business; uses the business identifier to perform revenue model judgment processing to obtain a revenue model; performs revenue calculation processing on the revenue model according to a preset revenue calculation strategy to obtain a revenue calculation type; uses the revenue calculation type and the transaction data to perform revenue compatibility processing to obtain a revenue file; and performs revenue display processing on the revenue file. Therefore, by performing revenue model judgment processing, revenue calculation processing, and revenue compatibility processing on the business identifier and transaction data to obtain a revenue model, revenue calculation type, and revenue file, the revenue model includes a first revenue model, a second revenue model, and a third revenue model. The revenue calculation type includes first natural day calculation, second natural day calculation, and transaction day calculation. The revenue model judgment processing and revenue calculation processing closely link the revenue model and revenue calculation type to simultaneously support natural day and transaction day calculations, and the revenue file is displayed, achieving compatible processing for direct sales and agency sales, thereby improving the stability, real-time performance, and accuracy of processing efficiency.

[0064] Figure 6 This is a schematic block diagram of a revenue data processing apparatus provided in an embodiment of the present invention. Figure 6 As shown, this embodiment of the invention provides a revenue data processing apparatus 700 for implementing the method described above. The revenue data processing apparatus 700 includes: The acquisition unit 701 is used to acquire the business identifier and transaction data corresponding to the target business when it is detected that a user has processed the target business; The revenue model determination unit 702 is used to perform revenue model determination processing using the business identifier to obtain a revenue model, wherein the revenue model includes a first revenue model, a second revenue model and a third revenue model. The revenue calculation unit 703 is used to perform revenue calculation processing on the revenue model according to a preset revenue calculation strategy to obtain a revenue calculation type, wherein the revenue calculation type is the first natural day calculation, the second natural day calculation, and the transaction day calculation. The revenue compatibility unit 704 is used to perform revenue compatibility processing using the revenue accounting type and the transaction activity data to obtain a revenue file; The revenue display unit 705 is used to perform revenue display processing on the revenue file.

[0065] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the above-mentioned device can be referred to the corresponding description in the foregoing method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0066] The above-described device can be implemented as a computer program, and the computer program can be implemented in, for example... Figure 7It runs on the computer device shown.

[0067] Please see Figure 7 , Figure 7 This is a schematic block diagram of an electronic device provided in an embodiment of the present invention. The electronic device 800 can be a terminal or a server. The terminal can be an electronic device with communication functions. The server can be a standalone server or a server cluster composed of multiple servers.

[0068] See Figure 7 The electronic device 800 includes a processor 802, a memory, and a network interface 805 connected via a system bus 801. The memory may include a non-volatile storage medium 803 and internal memory 804.

[0069] The non-volatile storage medium 803 may store an operating system 8031 ​​and a computer program 8032. The computer program 8032 includes program instructions that, when executed, cause the processor 802 to perform a revenue data processing method.

[0070] The processor 802 provides computing and control capabilities to support the operation of the entire electronic device 800.

[0071] The internal memory 804 provides an environment for the execution of the computer program 8032 in the non-volatile storage medium 803. When the computer program 8032 is executed by the processor 802, the processor 802 can perform a revenue data processing method.

[0072] This network interface 805 is used for network communication with other devices. Those skilled in the art will understand that... Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the electronic device 800 to which the present invention is applied. The specific electronic device 800 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0073] The processor 802 is used to run a computer program 8032 stored in the memory to perform the following steps: When a user is detected to be conducting a target service, the service identifier and transaction data corresponding to the target service are obtained; The revenue model is obtained by using the business identifier to determine the revenue model, which includes a first revenue model, a second revenue model, and a third revenue model. The revenue model is processed according to a preset revenue calculation strategy to obtain a revenue calculation type, which is a first natural day calculation, a second natural day calculation, and a transaction day calculation. A revenue file is obtained by performing revenue compatibility processing using the aforementioned revenue accounting type and the aforementioned transaction activity data; The revenue file is then processed to display the revenue.

[0074] It should be understood that, in this embodiment of the invention, the processor 802 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0075] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0076] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions. When executed by a processor, the program instructions cause the processor to perform the following steps: When a user is detected to be conducting a target service, the service identifier and transaction data corresponding to the target service are obtained; The revenue model is obtained by using the business identifier to determine the revenue model, which includes a first revenue model, a second revenue model, and a third revenue model. The revenue model is processed according to a preset revenue calculation strategy to obtain a revenue calculation type, which is a first natural day calculation, a second natural day calculation, and a transaction day calculation. A revenue file is obtained by performing revenue compatibility processing using the aforementioned revenue accounting type and the aforementioned transaction activity data; The revenue file is then processed to display the revenue.

[0077] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0078] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0079] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0080] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0081] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0082] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims. The software tools, models, or components appearing in the embodiments of the present invention are merely illustrative examples and do not represent actual use.

Claims

1. A method for processing revenue data, characterized in that, The revenue data processing method includes: When a user is detected to be conducting a target service, the service identifier and transaction data corresponding to the target service are obtained; The revenue model is obtained by using the business identifier to determine the revenue model, which includes a first revenue model, a second revenue model, and a third revenue model. The revenue model is processed according to a preset revenue calculation strategy to obtain a revenue calculation type, which is a first natural day calculation, a second natural day calculation, and a transaction day calculation. A revenue file is obtained by performing revenue compatibility processing using the aforementioned revenue accounting type and the aforementioned transaction activity data; The revenue file is then processed to display the revenue.

2. The method according to claim 1, characterized in that, The revenue calculation process, based on a preset revenue calculation strategy, yields a revenue calculation type. This revenue calculation type includes first-day calculation, second-day calculation, and transaction-day calculation, among others. When the revenue model is the first revenue model, the revenue accounting type is confirmed as the first natural day accounting. When the revenue model is the second revenue model, the revenue accounting type is confirmed as the second calendar day accounting. When the revenue model is the third revenue model, the revenue calculation type is confirmed as the transaction day calculation.

3. The method according to claim 1, characterized in that, The process of obtaining a revenue file by performing revenue compatibility processing using the revenue accounting type and the transaction activity data includes: When the revenue calculation type is first calendar day calculation and the current date is a transaction day, a first transaction calculation is performed based on the transaction activity data and the current date to obtain a first revenue file; when the revenue calculation type is first calendar day calculation and the current date is a non-transaction day, a second transaction calculation is performed based on the transaction activity data and the current date to obtain a second revenue file. When the revenue calculation type is the second natural day calculation, a third revenue file is obtained by performing a third transaction calculation based on the transaction activity data and the current date. When the revenue calculation type is transaction day calculation and the current date is a transaction day, a fourth revenue file is obtained by performing a fourth transaction calculation based on the transaction activity data and the current date; when the revenue calculation type is transaction day calculation and the current date is a non-transaction day, a fifth revenue file is obtained by performing a fifth transaction calculation based on the transaction activity data and the current date.

4. The method according to claim 3, characterized in that, When the revenue calculation type is first calendar day calculation and the current date is a transaction day, the first revenue file is obtained by performing first transaction calculation processing based on the transaction activity data and the current date, including: If the current date is a trading day and the previous calendar day is a trading day, then the previous calendar day will be taken as the first revenue attribution date; In the acquired push data, the business identifier in the transaction activity data is used to retrieve the first revenue data for the first revenue attribution date; The transaction activity data and the first revenue data are combined and processed to obtain the first revenue file.

5. The method according to claim 4, characterized in that, When the revenue calculation type is first calendar day calculation and the current date is a transaction day, the first revenue file is obtained by performing first transaction calculation processing based on the transaction activity data and the current date, and further includes: If the current date is a trading day and the previous calendar day is a non-trading day, then obtain the number M of non-trading days before the current date, and take the M non-trading days before the current date as the first revenue attribution date in sequence. In the pushed data, the business identifier in the transaction activity data is used to retrieve the first revenue data for each first revenue attribution date; The transaction activity data and each of the first revenue data are sequentially merged and calculated to obtain the first revenue file.

6. The method according to claim 4, characterized in that, The step of retrieving and obtaining the first revenue data for the first revenue attribution date from the acquired push data using the business identifier in the transaction activity data includes: In the pushed data, the first revenue attribution date is used as the second search condition. If the first revenue attribution date is found to be equal to the revenue date, the business revenue data corresponding to the revenue date is used as the first revenue data.

7. The method according to claim 1, characterized in that, The process of displaying revenue in the revenue file includes: The revenue file is then converted to obtain the target revenue data. The target revenue data will be pushed and displayed to the user.

8. A revenue data processing device, characterized in that, The revenue data processing device includes: The acquisition unit is used to acquire the business identifier and transaction data corresponding to the target business when it is detected that a user has processed the target business; A revenue model determination unit is used to perform revenue model determination processing using the business identifier to obtain a revenue model, wherein the revenue model includes a first revenue model, a second revenue model, and a third revenue model. The revenue calculation unit is used to perform revenue calculation processing on the revenue model according to a preset revenue calculation strategy to obtain the revenue calculation type, wherein the revenue calculation type is the first natural day calculation, the second natural day calculation, and the transaction day calculation. A revenue compatibility unit is used to perform revenue compatibility processing using the revenue accounting type and the transaction activity data to obtain a revenue file; The revenue display unit is used to display the revenue from the revenue file.

9. A computer device, characterized in that, The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1-7.

10. A storage medium, characterized in that, The storage medium stores a computer program, which includes program instructions that, when executed by a processor, can implement the method as described in any one of claims 1-7.

Images