Task execution method and device, equipment and medium

Abstract

The invention relates to a task execution method and device, equipment and a medium, and relates to the technical field of big data. The method comprises the following steps: in response to arrival of a target counting and extracting date in counting and extracting configuration information, executing an entry counting and extracting task so as to obtain a counting and extracting interval upper limit and a counting and extracting interval lower limit of a target counting and extracting interval associated with the target counting and extracting date from the counting and extracting configuration information; obtaining entry detail data of each day between the upper limit of the counting and extracting interval and the target counting and extracting date; summarizing the entry detail data of each day according to the target entry dimension to obtain entry summarized data of each day under the target entry dimension; according to the posting summary data of each day, generating a counting and extracting document in the target counting and extracting interval under the target posting dimension; and generating a task execution result according to the counting and extracting document. Therefore, the counting and extracting date and the associated counting and extracting interval are configured in a visual mode, and the counting and extracting document in the counting and extracting interval is generated, so that individual requirements of different users can be met, and the flexibility and the applicability of the method are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of big data technology, and in particular to a task execution method, device, equipment and medium. Background Art

[0002] Fund Transfer Pricing (FTP) is an internal pricing method for calculating the cost or benefit of business funds by transferring funds between the internal fund center and the business operation unit according to certain rules and in full amount. Among them, the price of full transfer of funds between the internal fund center and the business operation unit is called FTP price. FTP has been deeply applied in the risk pricing, performance evaluation, policy transmission, customer and product evaluation of financial institutions. It has achieved positive results in building a unified profit evaluation system for branches, departments, products and other dimensions, coordinating the business judgment of the head office and branches, enhancing the market price sensitivity of the whole bank, and realizing point-to-point policy transmission.

[0003] In the related art, financial institutions implement FTP management and record the FTP income and expenditure measurement results in accounting. Specifically, through hard coding, the accounting and accrual tasks are performed regularly on a monthly basis to generate FTP income and expenditure accrual documents from the beginning to the end of each month.

[0004] However, the above hard-coding method can only generate FTP income and expenditure accrual documents from the beginning to the end of each month, which has poor flexibility and cannot meet the application requirements in different business scenarios. Summary of the invention

[0005] The present disclosure provides a task execution method, device, equipment and medium to solve one of the technical problems in the related art at least to a certain extent. The technical solution of the present disclosure is as follows:

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided a task execution method, comprising:

[0007] In response to reaching a target provision date among a plurality of provision dates in provision configuration information configured for a financial institution, executing an accounting provision task to obtain an upper limit of a target provision interval and a lower limit of a target provision interval associated with the target provision date from the provision configuration information;

[0008] Obtaining detailed account entry data for each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution;

[0009] Summarizing the detailed accounting data of each day according to the target accounting dimension among the multiple accounting dimensions to obtain the accounting summary data of each day under the target accounting dimension;

[0010] According to the account summary data of each day, an accrual document within the target accrual range under the target account dimension is generated, and according to the accrual document, a task execution result is generated.

[0011] According to a second aspect of an embodiment of the present disclosure, there is provided a task execution device, including:

[0012] an execution module, configured to execute an accounting provision task in response to reaching a target provision date among a plurality of provision dates in provision configuration information configured for a financial institution, so as to obtain an upper limit of a target provision interval and a lower limit of a target provision interval associated with the target provision date from the provision configuration information;

[0013] An acquisition module, used to acquire detailed account entry data of each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution;

[0014] A summary module is used to summarize the detailed account data of each day according to the target account dimension among the multiple account dimensions to obtain the account summary data of each day under the target account dimension;

[0015] The first generating module is used to generate the provision documents within the target provision interval under the target accounting dimension according to the accounting summary data of each day, and generate the task execution result according to the provision documents.

[0016] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the task execution method proposed in the above-mentioned first aspect of the present disclosure.

[0017] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute the task execution method proposed in the first aspect of the present disclosure.

[0018] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising: a computer program, wherein when the computer program is executed by a processor, the task execution method as described in the above embodiment of the present disclosure is implemented.

[0019] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0020] Based on actual application needs or business needs, the user can visually configure the accrual date and the associated accrual range upper limit (which may not be the beginning of the month in which the accrual date is located, and may not be in the month in which the accrual date is located) and the accrual range lower limit (which may not be the end of the month in which the accrual date is located, and may not be in the month in which the accrual date is located) in a visual manner, and generate accrual documents between the upper limit of the accrual range and the lower limit of the accrual range, which can meet the personalized needs of different users and improve the flexibility and applicability of the method.

[0021] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0023] Figure 1 It is a flowchart of the task execution method shown in the first embodiment of the present disclosure.

[0024] Figure 2 It is a schematic diagram of the configuration interface shown in an embodiment of the present disclosure.

[0025] Figure 3 It is a flowchart of a task execution method shown in the second embodiment of the present disclosure.

[0026] Figure 4 It is a flowchart of a task execution method shown in the third embodiment of the present disclosure.

[0027] Figure 5 It is a flowchart of a task execution method shown in the fourth embodiment of the present disclosure.

[0028] Figure 6 It is a schematic diagram of the implementation principle of the embodiment of the present disclosure.

[0029] Figure 7 It is a structural diagram of a task execution device shown in the fifth embodiment of the present disclosure.

[0030] Figure 8 It is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0033] It should be noted that the acquisition, storage, use, and processing of data in the technical solution disclosed in this disclosure are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0034] It should also be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0035] It should also be noted that in the embodiments of the present disclosure, certain software, components, models and other existing solutions in the industry may be mentioned, which should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present disclosure, but it does not mean that the applicant has or will necessarily use the solution.

[0036] At present, when the actual daily FTP income and expenditure of the month has not been calculated, financial institutions need to estimate the FTP income and expenditure of the month in advance according to certain measurement rules and complete the provision and accounting. Among them, different financial institutions have different requirements for the measurement rules of the FTP income and expenditure provision amount of the month. Generally, there are two types:

[0037] The first method: For the time periods with available data in the current month, the daily FTP income and expenditure are calculated according to the actual pricing rules; for the time periods with no data in the current month, the actual FTP income and expenditure of the last day with available data in the current month is used as the estimated value of the daily FTP income and expenditure for the remaining days of the current month. The sum of the FTP income and expenditure of the two time periods is the FTP income and expenditure amount of the current month, which is all included in the accrued accounts.

[0038] That is, the amount of FTP income and expenditure recorded = the total of FTP income and expenditure actually incurred in the month + the total of FTP income and expenditure estimated to the end of the month.

[0039] Among them, the accrual rules are: for the time periods with available data in the current month, the daily FTP income and expenditure are calculated according to the actual pricing rules; for the time periods with no data in the current month, the actual FTP income and expenditure on the last day of available data is used as the estimated value of the daily FTP income and expenditure for the remaining days of the current month. The sum of the FTP income and expenditure of the two time periods is the FTP income and expenditure amount of the current month, which is all included in the accrual accounts.

[0040] Calculation formula: Accrued amount = actual FTP income and expenditure in the month + estimated FTP income and expenditure by the end of the month = ∑ actual daily FTP income and expenditure + actual FTP income and expenditure on the last day * remaining days in the month.

[0041] For example, assuming that the accrual date for March is set to March 23, the accrual amount for March = the total FTP income and expenditure amounts actually incurred each day from March 1 to March 23 + the FTP income and expenditure amounts incurred on March 23 * 8 days.

[0042] It should be noted that the FTP system can calculate the monthly accrual amount based on the above calculation rules on the accrual date of each month and generate accrual documents.

[0043] The second method: When the data for the accrual date set for this month are all in place, calculate the actual FTP income and expenditure each day from the last accrual date to the accrual date of this month and summarize them into the accounts.

[0044] That is, the amount of FTP revenue and expenditure recorded in the accounts = the total of FTP revenue and expenditure actually incurred each day between the accrual date of the previous month and the accrual date of this month.

[0045] Among them, the accrual rules are: when the accrual date data set for this month are all in place, calculate the actual daily FTP income and expenditure between the last accrual date and this month's accrual date and summarize them in the accounts.

[0046] Calculation formula: Accrual amount = total FTP income and expenditure actually incurred from the last accrual date to the current accrual date.

[0047] For example, assuming that the accrual date for February is set to February 22, and the accrual date for March is set to March 23, the accrual amount for March = the total of the actual FTP income and expenditure amounts incurred each day between February 23 and March 23.

[0048] In view of different FTP income and expenditure accounting and provision amount measurement rules, different codes are generally written in the background to implement different measurement rules. Only the monthly provision amount can be calculated fixedly, and different measurement rules cannot be implemented through flexible configuration of the front end.

[0049] Based on this, the present disclosure proposes a task execution method, apparatus, equipment and medium to improve the measurement of FTP income and expenditure accounting accrual amounts, and adds flexible configuration of FTP income and expenditure accounting accrual dates, as well as accrual intervals associated with the accrual dates, and implements different measurement rules through front-end configuration, that is, by flexibly configuring the monthly accrual dates and accrual intervals associated with the accrual dates through the front-end, to implement different measurement rules for the FTP income and expenditure accounting accrual amounts.

[0050] The following describes the task execution method, apparatus, device and medium of the embodiments of the present disclosure with reference to the accompanying drawings.

[0051] Figure 1 It is a flowchart of the task execution method shown in the first embodiment of the present disclosure.

[0052] The embodiment of the present disclosure takes the task execution method being configured in a task execution device as an example. The task execution device can be applied to any electronic device so that the electronic device can perform the task execution function.

[0053] Among them, the electronic device can be any device with computing capabilities, such as a personal computer, a mobile terminal, a server, etc. The mobile terminal can be, for example, a vehicle-mounted device, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, and other hardware devices with various operating systems, touch screens and / or display screens.

[0054] like Figure 1 As shown, the task execution method may include the following steps S11 to S14.

[0055] In step S11, in response to reaching a target provision date among multiple provision dates in the provision configuration information configured for the financial institution, an accounting provision task is executed to obtain an upper limit and a lower limit of a target provision interval associated with the target provision date from the provision configuration information.

[0056] Among them, the accrual configuration information is for the FTP income and expenditure accounting configuration of financial institutions, and the accrual configuration information includes multiple accrual dates, wherein the multiple accrual dates are in different months, and the accrual configuration information also includes the accrual interval upper limit and accrual interval lower limit associated with each accrual date.

[0057] Among them, the upper limit and lower limit of the accrual interval associated with each accrual date can be set according to actual application requirements or business requirements. It should be noted that the accrual date shall not be earlier than the upper limit of the associated accrual interval, and the upper limits of the accrual interval associated with different accrual dates may be different, and the lower limits of the accrual interval associated with different accrual dates may be different.

[0058] In an embodiment of the present disclosure, when a target accrual date among multiple accrual dates in the accrual configuration information configured for a financial institution (such as the accrual date of the current month) is reached and the transfer price measurement within FTP on the target accrual date is completed, an accounting accrual task can be executed to obtain the accrual interval upper limit and accrual interval lower limit of the accrual interval associated with the target accrual date (referred to as the target accrual interval in the present disclosure) from the accrual configuration information.

[0059] As an example, a user can Figure 2 The interface shown is used to configure the monthly accrual date, and to configure the upper and lower limits of the accrual interval associated with each accrual date.

[0060] It should be noted that Figure 2 The upper and lower limits of the accrual interval are only taken as the 25th of a certain month for example. In actual application, other dates can also be set, and the embodiments of the present disclosure do not limit this.

[0061] In step S12, detailed account entry data for each day between the upper limit of the provision interval and the target provision date is obtained from the business system of the financial institution.

[0062] In the disclosed embodiment, detailed account data (such as FTP detailed account data) for each day between the upper limit of the accrual interval and the target accrual date (including the day of the upper limit of the accrual interval and the day of the target accrual date) can be obtained from the business system of the financial institution.

[0063] In step S13, the detailed accounting data of each day are summarized according to the target accounting dimension among the multiple accounting dimensions to obtain the accounting summary data of each day under the target accounting dimension.

[0064] Among them, the various accounting dimensions include but are not limited to: position organization, currency, account, and regional type.

[0065] The target accounting dimension is an accounting dimension to be summarized selected by a user (relevant personnel of a financial institution, such as a business person) from among multiple accounting dimensions.

[0066] In the disclosed embodiment, the acquired detailed account data of each day may be summarized according to the target account dimension selected or set by the user to obtain the account summary data of each day under the target account dimension.

[0067] In step S14, according to the summary data of each day's accounting, an accrual document within the target accrual range under the target accounting dimension is generated, and according to the accrual document, a task execution result is generated.

[0068] In an embodiment of the present disclosure, an accrual document within a target accrual interval under a target accounting dimension can be generated based on daily accounting summary data, and an execution result of an accounting accrual task can be generated based on the accrual document within the target accrual interval, which is recorded as a task execution result in the present disclosure.

[0069] The task execution method of the embodiment of the present disclosure is that the user configures the accrual date and the associated accrual interval upper limit (which may not be the beginning of the month in which the accrual date is located, and may not be in the month in which the accrual date is located) and the accrual interval lower limit (which may not be the end of the month in which the accrual date is located, and may not be in the month in which the accrual date is located) in a visual manner based on actual application needs or business needs, and generates accrual documents between the upper limit of the accrual interval and the lower limit of the accrual interval, which can meet the personalized needs of different users and enhance the flexibility and applicability of the method.

[0070] The present disclosure provides another task execution method. Figure 3 It is a flowchart of a task execution method shown in the second embodiment of the present disclosure.

[0071] It should be noted that the task execution method can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment, or it can be executed in combination with any technical solution in the relevant technology, and the embodiments of the present disclosure are not limited to this.

[0072] like Figure 3 As shown, the task execution method may include the following steps S301 to S310.

[0073] In step S301, in response to reaching a target provision date among multiple provision dates in the provision configuration information configured for the financial institution, an accounting provision task is executed to obtain an upper limit and a lower limit of a target provision interval associated with the target provision date from the provision configuration information.

[0074] In step S302, detailed account entry data for each day between the upper limit of the provision interval and the target provision date is obtained from the business system of the financial institution.

[0075] For explanations of steps S301 to S302, reference may be made to the relevant descriptions in any embodiment of the present disclosure and will not be repeated here.

[0076] It should be noted that what is obtained from the business system of the financial institution is the full amount of daily accounting data, which may include accounting data that the user does not care about. Therefore, in order to improve the accuracy and pertinence of the execution of accounting and provision tasks, the obtained accounting data can be filtered.

[0077] That is, in any one of the embodiments of the present disclosure, the FTP pricing details results of each day between the upper limit of the accrual interval and the target accrual date can be obtained from the business system of the financial institution, wherein the FTP pricing details results include the capital cost or capital income calculated for various business activities of the financial institution based on the FTP rules configured for the financial institution. In the present disclosure, the FTP pricing details results of each day can be filtered based on the set filtering conditions to obtain the account entry details data for each day required by the user.

[0078] Among them, setting filtering conditions refers to filtering conditions pre-configured by the user. Exemplarily, setting filtering conditions may include: filtering the accounting data of a certain account, filtering the accounting data that does not meet specific standards, etc.

[0079] In this way, only the accounting details data required by the user can be retained, and the accrual document can be generated based on the accounting details data, so that the accrual document only contains relevant and necessary accounting data. This can not only improve the accuracy and pertinence of the execution of accounting and accrual tasks, but also meet the user's personalized needs and improve the user's experience.

[0080] In step S303, the account entry detail data of each day is summarized according to the target account entry dimension among the multiple account entry dimensions to obtain the account entry summary data of each day under the target account entry dimension.

[0081] For explanation of step S303, reference may be made to the relevant description in any embodiment of the present disclosure, and will not be repeated here.

[0082] In step S304, it is determined whether the target provision date is earlier than the lower limit of the provision interval. If so, steps S305 to S308 are executed; if not, step S309 is executed.

[0083] It should be noted that steps S305 to S308 and step S309 are two parallel implementation methods. In actual application, only one needs to be executed.

[0084] In step S305, the date difference between the target provision date and the lower limit of the provision interval is obtained.

[0085] In the embodiment of the present disclosure, when the target accrual date is earlier than the associated accrual interval lower limit, the date difference between the target accrual date and the associated accrual interval lower limit may be calculated.

[0086] In step S306, the account entry summary data of each day is summarized to obtain the first accrual sub-document between the upper limit of the accrual interval and the target accrual date.

[0087] As an example, if the target provision date is marked as T3 and the upper limit of the provision interval associated with the target provision date is T0, then the first provision sub-document between T0 and T3 can be: Daily account summary data.

[0088] Among them, T0≤T3.

[0089] In step S307, a second accrual sub-document between the target accrual date and the lower limit of the accrual interval is generated based on the accounting summary data of the target accrual date and the date difference.

[0090] As an example, if the lower limit of the accrual interval associated with the target accrual date is marked as T1, then the second accrual sub-document between T3 and T1 can be: (T1-T3)*the account summary data of T3.

[0091] In step S308, the first accrual sub-document and the second accrual sub-document are summarized to obtain the accrual documents within the target accrual interval.

[0092] As an example, the accrual documents within the target accrual range may be:

[0093]

[0094] In step S309, the account summary data of each day within the target provision interval is summarized to obtain the provision documents within the target provision interval.

[0095] In the disclosed embodiment, when the target provision date is not earlier than the lower limit of the provision interval, the account summary data of each day within the target provision interval can be directly summarized to obtain the provision document within the target provision interval.

[0096] As an example, the accrual documents within the target accrual range can be calculated according to the following formula:

[0097]

[0098] In step S310, a task execution result is generated according to the accrual document.

[0099] For the explanation of step S310, reference may be made to the relevant description in any embodiment of the present disclosure, and will not be repeated here.

[0100] In the task execution method of the disclosed embodiment, if the target accrual date is earlier than the associated accrual interval lower limit, the daily accounting summary data between (target accrual date + 1) and the accrual interval lower limit will be the same as the accounting summary data on the target accrual date by default, which can improve the effectiveness and rationality of accrual document generation.

[0101] If the target provision date is not earlier than the lower limit of the associated provision interval, the daily account summary data between the upper limit and lower limit of the provision interval configured by the user are directly summarized to obtain the provision documents within the target provision interval, which can improve the accuracy and reliability of the provision document generation.

[0102] The present disclosure provides another task execution method. Figure 4 It is a flowchart of a task execution method shown in the third embodiment of the present disclosure.

[0103] It should be noted that the task execution method can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment, or it can be executed in combination with any technical solution in the relevant technology, and the embodiments of the present disclosure are not limited to this.

[0104] like Figure 4 As shown, the task execution method may include the following steps S41 to S47.

[0105] In step S41, in response to reaching a target provision date among multiple provision dates in the provision configuration information configured for the financial institution, an accounting provision task is executed to obtain an upper limit and a lower limit of a target provision interval associated with the target provision date from the provision configuration information.

[0106] In step S42, detailed account entry data for each day between the upper limit of the provision interval and the target provision date is obtained from the business system of the financial institution.

[0107] In step S43, the detailed accounting data of each day are summarized according to the target accounting dimension among the multiple accounting dimensions to obtain the accounting summary data of each day under the target accounting dimension.

[0108] In step S44, based on the account summary data of each day, the FTP income and expenditure provision documents within the target provision range under the target account dimension are determined.

[0109] The explanation of steps S41 to S44 can be found in the relevant description in any embodiment of the present disclosure, and will not be repeated here.

[0110] In any one of the embodiments of the present disclosure, the account entry details data may be FTP income and expenditure account entry details data, and the accrual document may be FTP income and expenditure accrual document.

[0111] In step S45, the FTP income and FTP expenditure within the target provision interval are determined according to the FTP income and expenditure provision documents.

[0112] As an example, based on the income field, each record containing the income field can be determined from the FTP income and expenditure accrual document, and the amount in each record can be summarized to obtain the FTP income (or FTP income amount) within the target accrual range.

[0113] Similarly, based on the expenditure field, each record containing the expenditure field can be determined from the FTP revenue and expenditure accrual document, and the amount in each record can be summarized to obtain the FTP expenditure (or FTP expenditure amount) within the target accrual range.

[0114] In step S46, the FTP net income within the target provision interval is determined based on the FTP income and FTP expenditure.

[0115] As an example, FTP net income = FTP income - FTP expenses.

[0116] In step S47, a task execution result is generated according to the FTP net income.

[0117] In the disclosed embodiment, a task execution result may be generated based on the FTP net income, that is, the task execution result includes the FTP net income within the target accrual interval.

[0118] As a first possible implementation manner of any embodiment of the present disclosure, the task execution result may also be persistently stored.

[0119] For example, the FTP net income within the target provision interval in the task execution result can be stored in a data warehouse within the financial institution or a special financial management system for future analysis and reporting.

[0120] As a second possible implementation manner of any one of the embodiments of the present disclosure, a business report may also be generated according to the task execution result.

[0121] For example, based on the internal needs of the financial institution, an automated or semi-automated process can be used to generate business reports (such as monthly financial reports, performance appraisal reports, etc.) that include FTP net income in the task execution results, where FTP net income can be used as a key indicator in the business report.

[0122] As a third possible implementation manner of any embodiment of the present disclosure, the task execution result may also be visualized.

[0123] For example, the task execution results can be displayed through a dashboard so that relevant personnel of the financial institution can intuitively view the trend of FTP net income and its impact on the company's overall performance.

[0124] As a fourth possible implementation manner of any embodiment of the present disclosure, the task execution result may also be sent to a designated account or a designated device.

[0125] Exemplarily, the task execution result including the FTP net income can be sent to a designated account or designated device associated with relevant personnel of the financial institution. For example, the task execution result including the FTP net income can be sent to a designated account or designated device associated with relevant personnel of the financial department, so that these relevant personnel can check the accuracy of the data and make corresponding financial planning decisions based on it; for another example, the task execution result including the FTP net income can be sent to a designated account or designated device associated with relevant personnel of the risk management department, so that these relevant personnel can conduct risk assessment, especially liquidity risk and market risk.

[0126] It should be noted that, in actual application, the above-mentioned several possible implementation methods may be executed simultaneously, and the embodiments of the present disclosure do not limit this.

[0127] In summary, since FTP net income is not only an important indicator to measure the efficiency of internal capital operations of financial institutions, but also one of the foundations to support effective management and decision-making of the entire organization, the above-mentioned methods are used to synchronize the task execution results including FTP net income. This not only improves the accessibility and availability of data, but also enhances decision-making support, optimizes resource allocation, strengthens risk management, and improves communication and collaboration, which helps to achieve more efficient, transparent and sustainable operations.

[0128] The task execution method of the disclosed embodiment processes each record in the FTP revenue and expenditure accrual document, generates FTP net income within the target accrual range, and generates task execution results based on the FTP net income. This can provide in-depth insights into the internal capital flow and business unit performance of financial institutions, so that financial institutions can allocate resources more reasonably based on FTP net income, optimize resource allocation, improve decision-making quality, strengthen risk management, and meet regulatory requirements.

[0129] The present disclosure provides another task execution method. Figure 5 It is a flowchart of a task execution method shown in the fourth embodiment of the present disclosure.

[0130] It should be noted that the task execution method can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment, or it can be executed in combination with any technical solution in the relevant technology, and the embodiments of the present disclosure are not limited to this.

[0131] like Figure 5As shown, based on any of the above embodiments, the provision configuration information can be obtained by configuring the following steps S51 to S54.

[0132] In step S51, in response to a first configuration operation on the accrual date, accrual dates for a plurality of months are configured.

[0133] In an embodiment of the present disclosure, the user can configure the accrual date for each month based on a visual method. Accordingly, when a configuration operation for the accrual date (referred to as the first configuration operation in the present disclosure) is monitored, the accrual dates for multiple months can be configured in response to the first configuration operation.

[0134] In any embodiment of the present disclosure, after the user configures the accrual dates for multiple months, the following steps A to C may also be performed:

[0135] Step A: Count the number of months configured by the user.

[0136] Step B: When the number of months is less than the total number of months in a year (eg, 12 months), determine the target month for which the accrual date is not configured based on multiple months.

[0137] For example, assuming the months are January, March, May to December, the target months may be February and April.

[0138] Step C: Generate prompt information (referred to as the fourth prompt information in this disclosure) based on the target month; wherein the fourth prompt information is used to prompt that there is currently no configured target month, and configure the accrual date of the target month and the associated accrual interval upper limit and accrual interval lower limit.

[0139] In this way, the completeness of the configuration of the accrual date and the associated accrual interval can be improved, avoiding the omission of configuring the accrual date of a certain month, which results in the inability to execute the accounting accrual task of that month, and can further meet actual application needs or business needs.

[0140] In step S52, in response to the second configuration operation for the accrual interval, the accrual interval upper limit and the accrual interval lower limit of the accrual interval associated with the accrual date of each month are configured.

[0141] In an embodiment of the present disclosure, the user can configure the accrual interval associated with each accrual date based on a visual method. Accordingly, when a configuration operation for the accrual interval is monitored (referred to as the second configuration operation in the present disclosure), the accrual interval upper limit and accrual interval lower limit of the accrual interval associated with the accrual date of each month can be configured in response to the second configuration operation.

[0142] In step S53, the accrual date of each month, the associated accrual interval upper limit and the accrual interval lower limit are verified.

[0143] In the embodiment of the present disclosure, the accrual date of each month, the associated accrual interval upper limit and the accrual interval lower limit may be checked at the same time.

[0144] In any embodiment of the present disclosure, the following steps A' to D' may be used to verify the accrual date of each month:

[0145] Step A': for the accrual date of any month, determine the date configuration range that is suitable for the any month.

[0146] As an example, take the configuration interface as Figure 2 As shown in the example, the month is not editable by default, and the numbers (or integers) from 1 to 12 are displayed by default. For months 1, 3, 5, 7, 8, 10, and 12, the date configuration range is a number between 1 and 31; for months 4, 6, 9, and 11, the date configuration range is a number between 1 and 30; for month 2, the date configuration range is a number between 1 and 29.

[0147] Step B': Determine whether the provision date of any month is within the date configuration range, if so, execute step C', if not, execute step D'.

[0148] It should be noted that step D' and step C' are two parallel implementation methods. In actual application, only one needs to be executed.

[0149] Step C': If the accrual date of any month is within the date configuration range, it is determined that the accrual date of any month passes the verification.

[0150] That is, for months 1, 3, 5, 7, 8, 10, and 12, users can only fill in numbers between 1 and 31 as the accrual date for the corresponding months; for months 4, 6, 9, and 11, users can only fill in numbers between 1 and 30; for month 2, users can only fill in numbers between 1 and 29.

[0151] Step D': If the accrual date of any month is not within the date configuration range, it is determined that the accrual date of any month has failed the verification.

[0152] In summary, verifying the value of the accrual date for each month can improve the compliance and accuracy of the accrual date configuration.

[0153] In any embodiment of the present disclosure, the following steps A" to C' may be used to verify the upper limit and lower limit of the accrual interval associated with the accrual date of each month:

[0154] Step A”: For the upper limit of the accrual interval associated with the accrual date of any month (recorded as the first accrual interval upper limit in this disclosure), it can be determined whether the first accrual interval upper limit and the accrual interval lower limit associated with the accrual date of any month (recorded as the first accrual interval lower limit in this disclosure) are both between the any month and the previous month. If so, execute step B”; if not, execute step D” or step E”.

[0155] Step B”: If both are located at , determine whether the upper limit of the first accrual interval is not later than the lower limit of the first accrual interval. If so, execute step C”, if not, execute step D”.

[0156] Step C": If not later than, determine that both the first accrual interval upper limit and the first accrual interval lower limit pass the verification.

[0157] Step D": If the upper limit of the first accrual interval is not between any month and the previous month, or the upper limit of the first accrual interval is later than the lower limit of the first accrual interval, it is determined that the lower limit of the first accrual interval has not passed the verification.

[0158] Step E": If the lower limit of the first accrual interval is not between any month and the previous month, or the lower limit of the first accrual interval is earlier than the upper limit of the first accrual interval, it is determined that the lower limit of the first accrual interval has not passed the verification.

[0159] In summary, verifying the values ​​of the upper and lower limits of the accrual interval associated with the accrual date of each month can improve the compliance and accuracy of the accrual interval configuration.

[0160] In any embodiment of the present disclosure, if at least one of the accrual date of a certain month fails to pass the verification, the upper limit of a certain accrual interval fails to pass the verification, and the lower limit of a certain accrual interval fails to pass the verification, the user may be prompted to reconfigure the accrual date, the upper limit of the accrual interval, or the lower limit of the accrual interval, that is, in the present disclosure, at least one of the following steps a to c may also be performed:

[0161] Step a: If the accrual date of any month fails to pass the verification, a first prompt message is generated and displayed; wherein the first prompt message is used to prompt that the accrual date of any month fails to pass the verification, and prompt the allowable configuration range of the accrual date of any month.

[0162] Exemplarily, when the accrual date for February fails to pass verification, the first prompt information is used to indicate that the allowable configuration range of the accrual date for February is a number between 1 and 29.

[0163] Step b: If the upper limit of the first accrual interval fails to pass the verification, a second prompt message is generated and displayed; wherein the second prompt message is used to prompt that the upper limit of the first accrual interval fails to pass the verification, and prompt the allowable configuration range of the upper limit of the first accrual interval.

[0164] Still using the above example, if the upper limit of the first accrual interval associated with the accrual date in February fails to pass the verification, the allowed configuration range of the upper limit of the first accrual interval is: January 1 to February 29.

[0165] Step c: If the lower limit of the first accrual interval fails to pass the verification, a third prompt message is generated and displayed; wherein the third prompt message is used to prompt that the lower limit of the first accrual interval fails to pass the verification, and prompt the allowable configuration range of the lower limit of the first accrual interval.

[0166] Therefore, if at least one of any accrual date, the associated accrual interval upper limit and the accrual interval lower limit fails to pass the verification, the user will be promptly prompted, so that the user can correct the date that fails the verification in time, thereby improving the accuracy and rationality of the accrual configuration information configuration.

[0167] In step S54, the accrual configuration information is generated according to the verified accrual dates of each month, the associated accrual interval upper limit and the accrual interval lower limit.

[0168] In the embodiment of the present disclosure, the accrual configuration information may be generated according to the accrual dates of each month that pass the verification at the same time, the associated accrual interval upper limit, and the accrual interval lower limit.

[0169] The task execution method of the embodiment of the present disclosure allows the user to configure the accrual date in each month and the accrual interval upper limit and accrual interval lower limit associated with each accrual date in a visual configuration manner according to actual application needs or business needs, which can meet the personalized application needs of different users and improve the user experience.

[0170] In any embodiment of the present disclosure, the accrual date and accrual interval can be flexibly configured by the front desk to implement different measurement rules for FTP income and expenditure account accrual amounts. Figure 6 As shown, it mainly includes the following steps:

[0171] 1. Configuration of accrual date and accrual interval. For example, the configuration interface can be as follows: Figure 2 shown.

[0172] Among them, the functions of the configuration interface include: accrual date configuration, accrual interval upper limit configuration, accrual interval lower limit configuration, and saving.

[0173] The fields in the configuration interface are described in Table 1.

[0174] Table 1

[0175]

[0176] After the configuration of the accrual date and accrual interval is completed, the user can click the [Save] button to complete the save.

[0177] Verification rules: The accrual date, accrual interval upper limit, and accrual interval lower limit of each month must be configured in order to be saved successfully. Otherwise, a pop-up window will prompt "There are unconfigured months, please complete the configuration before saving."

[0178] 2. Generate detailed accounting data.

[0179] The daily FTP pricing details are filtered according to the filtering conditions set by the user, the data that is not recorded is filtered out, and the detailed data recorded is generated. For example, the processing frequency is monthly, and when the transfer price measurement within the FTP on the provision date of the corresponding month is completed, the detailed data recorded for each day within the provision period is generated.

[0180] 3. Generate accrual documents.

[0181] After the daily account entry details are generated, the daily account entry details are summarized according to the account entry dimension range, and then the FTP income and expenditure in the time dimension are summed up according to the accrual date and accrual interval configuration of the corresponding month. The details are as follows:

[0182] (1) Processing rules

[0183] a. After the daily entry details are generated, the daily entry details are summarized according to the summary entry dimensions set by the user to form daily entry summary data. The entry dimensions generally include: position organization, currency, account, and area type.

[0184] b. Process and summarize the daily account summary data in the time dimension according to the upper and lower limits of the provision interval set by the user. If the lower limit of the provision interval is later than the provision date, the daily account summary data between (Provision date + 1) and the lower limit of the provision interval will be the same as the account summary data on the provision date by default.

[0185] That is, if the upper limit of the accrual interval is marked as T0, the lower limit of the accrual interval is T1, and the accrual date is T3, then:

[0186] If T1≤T3, then:

[0187]

[0188] If T1>T3, then:

[0189]

[0190] c. For each record, process and generate the FTP net income field to form a complete accrual document.

[0191] That is: FTP net income = FTP income - FTP expenditure.

[0192] It should be noted that the processing frequency of accrual documents is monthly. After the transfer price measurement is completed within FTP on the accrual date of each month, the accrual documents are automatically generated according to the processing rules.

[0193] In summary, the accrual date and accrual interval can be flexibly configured through front-end visualization, and different FTP revenue and expenditure accounting accrual amount measurement rules can be implemented.

[0194] With the above Figures 1 to 6 Corresponding to the task execution method provided in the embodiment, the present disclosure also provides a task execution device. Figures 1 to 6 The task execution method provided in the embodiment corresponds to the task execution method, so the implementation method of the task execution method is also applicable to the task execution device provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

[0195] Figure 7 It is a structural diagram of a task execution device shown in the fifth embodiment of the present disclosure.

[0196] Reference Figure 7 The task execution device 700 may include: an execution module 710, an acquisition module 720, a summary module 730 and a first generation module 740.

[0197] The execution module 710 is used to execute the accounting provision task in response to reaching the target provision date among the multiple provision dates in the provision configuration information configured for the financial institution, so as to obtain the provision interval upper limit and the provision interval lower limit of the target provision interval associated with the target provision date from the provision configuration information;

[0198] The acquisition module 720 is used to obtain the detailed account entry data of each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution;

[0199] A summary module 730 is used to summarize the detailed account data of each day according to the target account dimension among the multiple account dimensions to obtain the account summary data of each day under the target account dimension;

[0200] The first generating module 740 is used to generate a provision document within a target provision interval under a target accounting dimension according to the accounting summary data of each day, and generate a task execution result according to the provision document.

[0201] In a possible implementation of the embodiment of the present disclosure, generation module 740 is used to: in response to the target provision date being earlier than the lower limit of the provision interval, obtain the date difference between the target provision date and the lower limit of the provision interval; summarize the account summary data of each day to obtain the first provision sub-document between the upper limit of the provision interval and the target provision date; generate the second provision sub-document between the target provision date and the lower limit of the provision interval based on the account summary data and the date difference of the target provision date; summarize the first provision sub-document and the second provision sub-document to obtain the provision document within the target provision interval.

[0202] In a possible implementation of the embodiment of the present disclosure, the generation module 740 is also used to: in response to the target provision date being not earlier than the lower limit of the provision interval, summarize the accounting summary data of each day within the target provision interval to obtain the provision document within the target provision interval.

[0203] In a possible implementation of the embodiment of the present disclosure, a generation module 740 is used to: determine FTP income and FTP expenditure within a target accrual interval based on FTP income and expenditure accrual documents; determine FTP net income within the target accrual interval based on FTP income and FTP expenditure; and generate a task execution result based on the FTP net income.

[0204] In a possible implementation of the embodiment of the present disclosure, the provision configuration information is obtained by configuring the following modules:

[0205] A first configuration module, configured to configure accrual dates for a plurality of months in response to a first configuration operation on the accrual date;

[0206] A second configuration module, configured to configure an upper limit and a lower limit of an accrual interval associated with an accrual date of each month in response to a second configuration operation on the accrual interval;

[0207] The verification module is used to verify the accrual date of each month, the upper limit of the associated accrual interval, and the lower limit of the accrual interval;

[0208] The second generation module is used to generate the accrual configuration information according to the accrual date of each month that has passed the verification, the associated accrual interval upper limit and the accrual interval lower limit.

[0209] In a possible implementation of the embodiment of the present disclosure, the verification module is used to: determine the date configuration range that is compatible with the accrual date of any month; if the accrual date of any month is within the date configuration range, then determine that the accrual date of any month has passed the verification; if the accrual date of any month is not within the date configuration range, then determine that the accrual date of any month has not passed the verification.

[0210] In a possible implementation of the embodiment of the present disclosure, the verification module is used to: determine whether the upper limit of the first accrual interval and the lower limit of the first accrual interval are both located between any month and the previous month; wherein the upper limit of the first accrual interval refers to the upper limit of the accrual interval associated with the accrual date of any month, and the lower limit of the first accrual interval refers to the lower limit of the accrual interval associated with the accrual date of any month; if both are located at, then determine whether the upper limit of the first accrual interval is not later than the lower limit of the first accrual interval; if not later than, then determine that both the upper limit of the first accrual interval and the lower limit of the first accrual interval have passed the verification; if the upper limit of the first accrual interval is not located between any month and the previous month, or, the upper limit of the first accrual interval is later than the lower limit of the first accrual interval, then determine that the lower limit of the first accrual interval has not passed the verification; if the lower limit of the first accrual interval is not located between any month and the previous month, or, the lower limit of the first accrual interval is earlier than the upper limit of the first accrual interval, then determine that the lower limit of the first accrual interval has not passed the verification.

[0211] In a possible implementation of the embodiment of the present disclosure, the task execution device 700 may include:

[0212] The first processing module is used to execute at least one of the following: if the accrual date of any month fails to pass the verification, a first prompt message is generated and displayed; wherein the first prompt message is used to prompt that the accrual date of any month fails to pass the verification, and prompt the allowed configuration range of the accrual date of any month; if the upper limit of the first accrual interval fails to pass the verification, a second prompt message is generated and displayed; wherein the second prompt message is used to prompt that the upper limit of the first accrual interval fails to pass the verification, and prompt the allowed configuration range of the upper limit of the first accrual interval; if the lower limit of the first accrual interval fails to pass the verification, a third prompt message is generated and displayed; wherein the third prompt message is used to prompt that the lower limit of the first accrual interval fails to pass the verification, and prompt the allowed configuration range of the lower limit of the first accrual interval.

[0213] In a possible implementation of the embodiment of the present disclosure, the task execution device 700 may include:

[0214] The second processing module is used to obtain the number of months of multiple months; when the number of months is less than the total number of months in a year, determine the target month for which the accrual date is not configured based on the multiple months; generate the fourth prompt information based on the target month; wherein the fourth prompt information is used to prompt that there is currently no configured target month, and configure the accrual date of the target month and the associated accrual interval upper limit and accrual interval lower limit.

[0215] In a possible implementation of the embodiment of the present disclosure, the acquisition module 720 is used to: obtain the FTP pricing details results of each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution; wherein the FTP pricing details results include the capital cost or capital income calculated for various business activities of the financial institution according to the FTP rules; based on the set filtering conditions, the FTP pricing details results of each day are filtered to obtain the account entry details data of each day.

[0216] In a possible implementation of the embodiment of the present disclosure, the task execution device 700 may include:

[0217] The third processing module is used to perform at least one of the following: persistent storage of task execution results; generation of business reports based on task execution results; visual display of task execution results; and sending task execution results to a designated account or a designated device.

[0218] The task execution device of the embodiment of the present disclosure allows the user to configure the accrual date and the associated accrual interval upper limit (which may not be the beginning of the month in which the accrual date is located, and may not be in the month in which the accrual date is located) and the accrual interval lower limit (which may not be the end of the month in which the accrual date is located, and may not be in the month in which the accrual date is located) in a visual manner based on actual application needs or business needs, and generates accrual documents between the upper limit of the accrual interval and the lower limit of the accrual interval, which can meet the personalized needs of different users and enhance the flexibility and applicability of the method.

[0219] In an exemplary embodiment, the present disclosure also provides an electronic device.

[0220] Among them, electronic equipment includes:

[0221] processor;

[0222] a memory for storing processor-executable instructions;

[0223] The processor is configured to execute instructions to implement the task execution method proposed in any of the aforementioned embodiments of the present disclosure.

[0224] As an example, Figure 8 is a schematic diagram of the structure of an electronic device 800 shown in an exemplary embodiment of the present disclosure, such as Figure 8 As shown, the electronic device 800 may further include:

[0225] The memory 810 and the processor 820, a bus 830 connecting different components (including the memory 810 and the processor 820), the memory 810 stores a computer program, and when the processor 820 executes the program, the task execution method described in any embodiment of the present disclosure is implemented.

[0226] Bus 830 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0227] The electronic device 800 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 800, including volatile and non-volatile media, removable and non-removable media.

[0228] The memory 810 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 840 and / or cache memory 850. The server 800 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 860 may be used to read and write non-removable, non-volatile magnetic media ( Figure 8 not shown, usually called a "hard drive"). Although Figure 8 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 830 via one or more data medium interfaces. The memory 810 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0229] A program / utility 880 having a set (at least one) of program modules 870 may be stored, for example, in the memory 810, such program modules 870 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 870 generally perform the functions and / or methods of the embodiments described in the present disclosure.

[0230] The electronic device 800 may also communicate with one or more external devices 890 (e.g., keyboard, pointing device, display 891, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 800, and / or may communicate with any device that enables the electronic device 800 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed via an input / output (I / O) interface 892. Furthermore, the electronic device 800 may also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and / or public network, such as the Internet) via a network adapter 893. As shown, the network adapter 893 communicates with other modules of the electronic device 800 via a bus 830. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0231] The processor 820 executes various functional applications and tasks by running programs stored in the memory 810 .

[0232] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the task execution method of any embodiment of the present disclosure, and will not be repeated here.

[0233] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, and the above instructions can be executed by a processor of an electronic device to complete the method proposed in any of the above embodiments. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0234] In an exemplary embodiment, a computer program product is also provided, including a computer program / instruction, wherein the computer program / instruction implements the method proposed in any of the above embodiments when executed by a processor.

[0235] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0236] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A task execution method, characterized in that: include: In response to reaching a target provision date among a plurality of provision dates in provision configuration information configured for a financial institution, executing an accounting provision task to obtain an upper limit of a target provision interval and a lower limit of a target provision interval associated with the target provision date from the provision configuration information; Obtaining detailed account entry data for each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution; Summarizing the detailed accounting data of each day according to the target accounting dimension among the multiple accounting dimensions to obtain the accounting summary data of each day under the target accounting dimension; According to the account summary data of each day, an accrual document within the target accrual range under the target account dimension is generated, and according to the accrual document, a task execution result is generated.

2. The method according to claim 1, characterized in that The step of generating the provision document within the target provision range under the target provision dimension according to the summary data of each day's entry includes: In response to the target provision date being earlier than the lower limit of the provision interval, obtaining a date difference between the target provision date and the lower limit of the provision interval; Summarize the account entry summary data of each day to obtain the first accrual sub-document between the upper limit of the accrual interval and the target accrual date; Generate a second accrual sub-document between the target accrual date and the lower limit of the accrual interval according to the account summary data of the target accrual date and the date difference; The first accrual sub-document and the second accrual sub-document are aggregated to obtain accrual documents within the target accrual interval.

3. The method according to claim 2, characterized in that The step of generating, based on the daily account summary data, the provision documents within the target provision range under the target account dimension, further includes: In response to the target provision date being not earlier than the lower limit of the provision interval, the account entry summary data of each day within the target provision interval are summarized to obtain the provision document within the target provision interval.

4. The method according to claim 1, characterized in that: The entry details data are the internal funds transfer price FTP income and expenditure entry details data, and the provision document is the FTP income and expenditure provision document; The step of generating a task execution result according to the provision document includes: Determine the FTP income and FTP expenditure within the target provision range according to the FTP income and expenditure provision documents; Determine the FTP net income within the target provision interval based on the FTP income and the FTP expenditure; The task execution result is generated according to the FTP net income.

5. The method according to claim 1, characterized in that: The provision configuration information is configured by the following steps: In response to a first configuration operation on the accrual date, configuring accrual dates for a plurality of months; In response to a second configuration operation for the accrual interval, configuring an accrual interval upper limit and an accrual interval lower limit of the accrual interval associated with the accrual date of each month; Verify the accrual date of each month, the upper limit of the associated accrual interval, and the lower limit of the accrual interval; The accrual configuration information is generated according to the verified accrual dates of each month, the associated accrual interval upper limit and the accrual interval lower limit.

6. The method according to claim 5, characterized in that Verify the accrual date for each month, including: For the accrual date of any month, determine the date configuration range that is suitable for any month; If the accrual date of any month is within the date configuration range, it is determined that the accrual date of any month passes the verification; If the accrual date of any month is not within the date configuration range, it is determined that the accrual date of any month has failed the verification.

7. The method according to claim 6, characterized in that Verify the upper and lower limits of the accrual interval associated with the accrual date of each month, including: Determine whether the first accrual interval upper limit and the first accrual interval lower limit are both between the any month and the previous month; wherein the first accrual interval upper limit refers to the accrual interval upper limit associated with the accrual date of the any month, and the first accrual interval lower limit refers to the accrual interval lower limit associated with the accrual date of the any month; If both are within , determining whether the first provision interval upper limit is not later than the first provision interval lower limit; If it is not later than, determining that both the first provision interval upper limit and the first provision interval lower limit have passed the verification; If the first accrual interval upper limit is not between the any month and the previous month, or the first accrual interval upper limit is later than the first accrual interval lower limit, it is determined that the first accrual interval lower limit has not passed the verification; If the first accrual interval lower limit is not between any month and the previous month, or the first accrual interval lower limit is earlier than the first accrual interval upper limit, it is determined that the first accrual interval lower limit has not passed the verification.

8. The method according to claim 7, characterized in that The method further comprises at least one of the following: If the accrual date of any month fails to pass the verification, a first prompt message is generated and displayed; wherein the first prompt message is used to prompt that the accrual date of any month fails to pass the verification, and prompt the allowable configuration range of the accrual date of any month; If the first accrual interval upper limit fails to pass the verification, a second prompt message is generated and displayed; wherein the second prompt message is used to prompt that the first accrual interval upper limit fails to pass the verification, and prompt the allowable configuration range of the first accrual interval upper limit; If the lower limit of the first accrual interval fails to pass the verification, a third prompt message is generated and displayed; wherein the third prompt message is used to prompt that the lower limit of the first accrual interval fails to pass the verification, and to prompt the allowable configuration range of the lower limit of the first accrual interval.

9. The method according to claim 6, characterized in that The method further comprises: Get the month number of the multiple months; In the case where the number of months is less than the total number of months included in a year, determining a target month for which no provision date is configured based on the multiple months; Generating fourth prompt information according to the target month; The fourth prompt information is used to prompt that there is currently no configured target month, and to configure the accrual date of the target month and the associated accrual interval upper limit and accrual interval lower limit.

10. The method according to any one of claims 1 to 9, characterized in that The step of obtaining detailed account entry data of each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution includes: Obtaining, from the business system of the financial institution, detailed FTP pricing results for each day between the upper limit of the provision interval and the target provision date; wherein the detailed FTP pricing results include the capital cost or capital income calculated for various business activities of the financial institution according to the FTP rules; Based on the set filtering conditions, the FTP pricing details of each day are filtered to obtain the detailed account data of each day.

11. The method according to any one of claims 1 to 9, characterized in that The method further comprises at least one of the following: Persistently storing the task execution results; Generate a business report based on the task execution results; Visually display the task execution results; The task execution result is sent to a specified account or a specified device.

12. A task execution device, characterized in that: include: an execution module, configured to execute an accounting provision task in response to reaching a target provision date among a plurality of provision dates in provision configuration information configured for a financial institution, so as to obtain an upper limit of a target provision interval and a lower limit of a target provision interval associated with the target provision date from the provision configuration information; An acquisition module, used to acquire detailed account entry data of each day between the upper limit of the provision interval and the target provision date from the business system of the financial institution; A summary module is used to summarize the detailed account data of each day according to the target account dimension among the multiple account dimensions to obtain the account summary data of each day under the target account dimension; The first generating module is used to generate the provision documents within the target provision interval under the target accounting dimension according to the accounting summary data of each day, and generate the task execution result according to the provision documents.

13. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the task execution method according to any one of claims 1 to 11. 14 . A computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the task execution method according to any one of claims 1 to 11.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the task execution method according to any one of claims 1 to 11 is implemented.

Images