Cross-organizational account task management method, device, and equipment, and storage medium

Abstract

The application provides a cross-organization account closing task management method and device, equipment and a storage medium. The cross-organization account closing task management method comprises the following steps: obtaining an account closing request of a target account closing organization in a target time period under a target business board; obtaining an account closing task list belonging to the target business board in the target time period according to the account closing request, wherein the account closing task list comprises a plurality of account closing tasks of a plurality of account closing organizations; publishing the account closing task list to the plurality of account closing organizations, so that each account closing organization of the plurality of account closing organizations executes an account closing task associated with itself in the account closing task list; and obtaining a completion state of each account closing task in the account closing task list executed by each account closing organization. The application can provide a unified task list for different organizations, so that different organizations complete their respective corresponding tasks under the unified task list, and managers can realize cross-organization task management in a unified management system, thereby improving management efficiency.

Description

Technical Field

[0001] This application relates to the field of information technology software, specifically to a method, apparatus, device, and storage medium for cross-organizational accounting task management. Background Technology

[0002] With the development of information technology, information-based and automated process management is being used more and more widely in different companies. However, different companies often have their own unique process management methods and systems. When faced with the need to implement unified process management for different companies or target organizations, the lack of unified process management will lead to the following problems:

[0003] There are many process management systems, but they lack unified control. Different process systems have different ways of connecting processes, which makes it difficult to unify processes. Alternatively, manual management is used, but when manual management is used, it is still necessary to log in to different process management pages, which affects the smoothness of operation. In addition, there are scenarios where errors in human input data due to manual execution lead to incorrect results.

[0004] When information transmission is inaccurate or there are too many processes that cannot be standardized, manual process operations may sometimes be implemented, relying on offline emails to be sent to different personnel. The method of email transmission is affected by the accuracy of email addresses and personnel job changes, which may result in untimely or incorrect information transmission.

[0005] The execution process is opaque, with different process management systems corresponding to different executors. There is no effective visualization management of task progress and schedule, and managers cannot check the progress or identify potential risks at any time.

[0006] Therefore, how to implement unified task process management across different companies has become a technical problem to be solved. Summary of the Invention

[0007] This application provides a cross-organizational closing task management method. By providing a unified task list to different organizations, different organizations can complete their respective tasks under the unified task list. This allows managers to achieve cross-organizational task management in a unified standard management interface or system, avoiding the need for managers to manage tasks according to the management methods or systems of different organizations, thus improving management efficiency.

[0008] On the one hand, this application provides a method for cross-organizational closing task management, the method comprising:

[0009] Obtain the closing requests from the target closing organization within the target business segment and for the target time period;

[0010] Based on the closing request, a closing task list belonging to the target business segment within the target time period is created, and the closing task list includes multiple closing tasks from multiple closing organizations.

[0011] The closing task list is published to the plurality of closing organizations, so that each of the plurality of closing organizations executes the closing tasks associated with itself in the closing task list;

[0012] Obtain the completion status of each closing task in the closing task list executed by each closing organization.

[0013] In some embodiments of this application, before obtaining the closing task request of the target closing organization within a target business segment and a target time period, the method further includes:

[0014] Define closing task master data to represent each closing task, wherein the closing task master data includes information about the closing organization, information about the business segment to which the closing task belongs, and information about the source of the closing task;

[0015] When a request to create a closing task is received, the closing task is created based on the closing task master data.

[0016] In some embodiments of this application, before obtaining the list of closing tasks belonging to the target business segment within the target time period according to the closing request, the method further includes:

[0017] Define the coding strategy for closing tasks;

[0018] The pre-defined closing tasks of various types are encoded according to the closing task coding strategy to obtain the closing task codes of various types.

[0019] By using various types of closing task codes, we define the closing task templates corresponding to each business segment, thus obtaining the closing task templates for each business segment.

[0020] In some embodiments of this application, the step of creating a list of closing tasks belonging to the target business segment within the target time period based on the closing request includes:

[0021] Through the multiple closing organizations and the multiple closing tasks, closing organization permissions are set for each closing task corresponding to each target closing organization. The closing organization permissions include browsing permissions and operation permissions of the closing organization.

[0022] Based on the browsing permissions and operation permissions, obtain the list of closing tasks.

[0023] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method further includes:

[0024] Determine the completion status of each closing task in the closing task list;

[0025] Based on the completion status of each closing task, the completion status of the target closing organization in executing the closing task list is determined.

[0026] In some embodiments of this application, determining the completion status of the target closing organization's execution of the closing task list based on the completion status of each closing task includes:

[0027] If at least one closing task in the closing task list has been completed, the closing task list is determined to be in an active state.

[0028] If all tasks in the closing task list have been completed, the closing task list is determined to be in a completed state.

[0029] If the current task in the closing task list is in a paused state, then the closing task list is determined to be in a paused state.

[0030] If the closing task list is not published to the target closing organization after it is created, the closing task list is determined to be in an unpublished state.

[0031] If the closing task list has been created and published to the target closing organization, the closing task list is determined to be in a published state.

[0032] In some embodiments of this application, after determining the completion status of the target closing organization's execution of the closing task list based on the completion status of each closing task, the method further includes:

[0033] If the closing task list is active or published, check the status of the currently executing closing tasks in the closing task list according to a preset period and update the completion status of the closing task list.

[0034] In some embodiments of this application, the step of checking the status of currently executing closing tasks in the closing task list at a preset period includes:

[0035] The task status of each closing task in the closing task list is obtained according to a preset cycle.

[0036] Based on the task status, update the completion status of the target closing organization in executing the closing task list.

[0037] In some embodiments of this application, obtaining the task status of each closing task in the closing task list according to a preset period includes:

[0038] If the current closing task is being processed, the task status of the current closing task is determined to be "processing".

[0039] If the current closing task has not yet started processing, the task status of the current closing task is determined to be unprocessed.

[0040] If the current closing task has been completed without errors, the task status of the current closing task is determined to be "completed without errors".

[0041] If the current closing task has been completed but there is a warning message, and this does not affect the actual completion, then the task status of the current closing task is determined to be "completed with warning".

[0042] If the current closing task has been completed but the returned execution result is an error, when the closing task is executed again in a subsequent run, the task status of the current closing task should be determined to be "completed but error exists".

[0043] If the current closing task has been checked and completed normally, the task status of the current closing task is determined to be "checked".

[0044] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method further includes:

[0045] If the task status of the preceding closing task is the completed without error, the completed with warning, or the checked, the subsequent closing task can change the task status when a task status change request is obtained.

[0046] If the task status of the pre-closing task is either "processing" or "completed with an error", the post-closing task cannot change its task status when a task status change request is obtained.

[0047] If the task status of the preceding task changes when the subsequent closing task has been completed, the task status of the subsequent closing task automatically changes to the "completed but error exists" state when a task status change request is obtained.

[0048] If the task status of the pre-closing task is "completed without errors" or "checked", the system prompts the user whether the post-closing task should start immediately. If the user selects "yes", the post-closing task starts. If the user selects "no", the post-closing task ends.

[0049] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method further includes:

[0050] When the completion status of each actual closing task in the closing task list is consistent with the current completion status of each closing task, the execution of the closing task list ends.

[0051] If the current completion status of at least one closing task is inconsistent with the actual closing completion status, prompt whether to complete the closing task list.

[0052] If the user selects "yes", the execution of the closing task list will end.

[0053] If the user selects "no", continue executing the closing task list.

[0054] On the other hand, this application also provides a method for cross-organizational closing task management, the method comprising:

[0055] Obtain multiple closing requests from the target closing organization during the second target time period;

[0056] Based on the multiple closing requests, create a list of closing tasks belonging to each business segment within the second target time period. Each list of closing tasks includes multiple closing tasks from multiple target closing organizations.

[0057] The various closing task lists are published to the multiple target closing organizations, so that the multiple target closing organizations execute the closing tasks associated with themselves in the closing task lists associated with themselves.

[0058] Obtain the completion status of each closing task in the closing task list associated with each of the multiple target closing organizations.

[0059] On the other hand, this application also provides a cross-organizational task management device, the cross-organizational task management device comprising:

[0060] The first acquisition module is used to acquire the closing requests of the target closing organization within the target business segment and the target time period.

[0061] A creation module is used to create a list of closing tasks belonging to the target business segment within the target time period based on the closing request. The list of closing tasks includes multiple closing tasks from multiple closing organizations.

[0062] The publishing module is used to publish the closing task list to the multiple closing organizations, so that each closing organization executes the closing tasks associated with itself in the closing task list;

[0063] The second acquisition module is used to acquire the completion status of each closing task in the closing task list executed by each closing organization.

[0064] In some embodiments of this application, the first acquisition module is specifically used for:

[0065] Retrieve the closing requests of the target closing organization within the target business segment and the target time period.

[0066] In some embodiments of this application, before obtaining the list of closing tasks belonging to the target business segment within the target time period according to the closing request;

[0067] The first acquisition module is specifically used for:

[0068] By using various types of closing task codes, we define the closing task templates corresponding to each business segment, thus obtaining the closing task templates for each business segment.

[0069] In some embodiments of this application, the step of creating a list of closing tasks belonging to the target business segment within the target time period according to the closing request, wherein the list of closing tasks includes multiple closing tasks of multiple closing organizations;

[0070] The creation module is specifically used for:

[0071] Based on the browsing permissions and operation permissions, obtain the list of closing tasks.

[0072] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the second obtaining module is specifically used for:

[0073] Determine the completion status of each closing task in the closing task list;

[0074] Based on the completion status of each closing task, the completion status of the target closing organization in executing the closing task list is determined.

[0075] In some embodiments of this application, the step of checking the currently executing closing tasks in the closing task list according to a preset period is described.

[0076] The second acquisition module is also specifically used for:

[0077] The task status of each closing task in the closing task list is obtained according to a preset cycle.

[0078] On the other hand, this application also provides a cross-organizational task management device, the cross-organizational task management device comprising:

[0079] One or more processors;

[0080] Memory; and

[0081] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement any one of the cross-organizational closing task management methods.

[0082] On the other hand, this application also provides a computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to perform steps in any of the cross-organizational closing task management methods described herein.

[0083] This application sends a unified task list to different target organizations, enabling them to complete the execution and operation of related tasks on a unified task template. This allows managers to manage different organizations through a unified process system, improving efficiency compared to managing different process systems. Furthermore, executing task management on a unified task management system allows managers to access all task execution details, increasing transparency. After task execution is completed, results are generated, allowing managers to track the completion status of all tasks and control process risks. Attached Figure Description

[0084] Figure 1 This is a schematic diagram of a cross-organizational task management system provided in the embodiments of this application;

[0085] Figure 2 This is a schematic flowchart of one embodiment of the cross-organizational task management method in this application.

[0086] Figure 3 This is a schematic diagram of one embodiment of creating a closing task in this application;

[0087] Figure 4 This is a flowchart of one embodiment of obtaining the closing task template in this application;

[0088] Figure 5 This is a schematic diagram of an embodiment of step 202 in this application;

[0089] Figure 6 This is a flowchart of an embodiment of determining the task status of the closing task list in this application;

[0090] Figure 7 This is a flowchart of one embodiment of closing the account closure task list in this application;

[0091] Figure 8This is a schematic diagram of an embodiment of a cross-organizational task management method in this application.

[0092] Figure 9 This is a schematic diagram of an embodiment of the device for cross-organizational task management in this application.

[0093] Figure 10 This is a schematic diagram of an embodiment of a device for cross-organizational task management in this application. Detailed Implementation

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

[0095] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0096] In this application, the term "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes are not described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0097] This application provides a cross-organizational task management method, apparatus, device, and storage medium, which will be described in detail below.

[0098] Please see Figure 1 , Figure 1This is a schematic diagram illustrating a scenario of the cross-organizational task management method provided in an embodiment of this application. The cross-organizational task management system may include a terminal device 100 and a backend device 200. The terminal device 100 and the backend device 200 are communicatively connected. The terminal device 100 can transmit data to the backend device 200, and the backend device 200 can also transmit data to the terminal device 100. Figure 1 Terminal device 100 can transmit the obtained real-time data to backend device 200; backend device 200 can calculate the cross-organization task management scheme and then transmit the cross-organization task management scheme to terminal device 100.

[0099] In this embodiment of the application, the terminal device 100 may include, but is not limited to, desktop computers, portable computers, network servers, PDAs (personal digital assistants), mobile phones, tablet computers, wireless terminal devices, communication devices, embedded devices, etc.

[0100] In this embodiment, the aforementioned backend device 200 can be an independent server, or a server network or server cluster composed of servers. For example, the cross-organizational task management device 200 described in this embodiment includes, but is not limited to, computers, network hosts, single network servers, multiple network server sets, or cloud servers composed of multiple servers. The cloud server is composed of a large number of computers or network servers based on cloud computing.

[0101] In the embodiments of this application, the terminal device 100 and the backend device 200 can communicate through any communication method, including but not limited to mobile communication based on the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), and Worldwide Interoperability for Microwave Access (WiMAX), or computer network communication based on the TCP / IP Protocol Suite (TCP / IP) and User Datagram Protocol (UDP).

[0102] Those skilled in the art will understand that Figure 1 The application environment shown is merely one application scenario of the solution in this application and does not constitute a limitation on the application scenario of the solution in this application. Other application environments may include those that are more specific to this application. Figure 1 The number of more or fewer terminal devices and backend devices shown, for exampleFigure 1 Only one terminal device or backend device is shown in the document. The cross-organizational task management system may also include one or more other terminal devices and backend devices that can process data, which are not specifically limited here.

[0103] In addition, such as Figure 1 As shown, the cross-organizational task management system may also include a memory 300 for storing data, such as data on scheduling processes and scheduling results in cross-organizational task management.

[0104] It should be noted that, Figure 1 The schematic diagram of the cross-organizational task management system shown is merely an example. The cross-organizational task management system and scenario described in this application embodiment are intended to more clearly illustrate the technical solutions of this application embodiment and do not constitute a limitation on the technical solutions provided in this application embodiment. As those skilled in the art will know, with the evolution of cross-organizational task management systems and the emergence of new business scenarios, the technical solutions provided in this application embodiment are also applicable to similar technical problems.

[0105] like Figure 2 As shown, Figure 2 This is a flowchart illustrating one embodiment of the cross-organizational task management method in this application. The cross-organizational task management method may include the following steps 201-204:

[0106] 201. Obtain the closing requests of the target closing organization within the target business segment and the target time period.

[0107] In this embodiment of the application, the method of obtaining the closing request can be to directly obtain the corresponding computer instruction for the closing request, or to indirectly obtain the corresponding computer instruction for the closing request from other memory. The memory can be a general memory or a high-speed cache memory, such as a cache memory. It should be noted that the method of obtaining the closing request described in this step is only one specific implementation, and it does not limit the other methods of obtaining the closing request.

[0108] Closing the accounts refers to the accounting function within a unit of time before activating new accounts. The target time period can be annual, monthly, etc. After closing the accounts within the unit of time, accounting-related tasks such as auditing, recording, and carry-forward are generally not possible. The closing account task request mentioned in this step is a prerequisite for performing the closing account task. The closing account task request can be a computer command or a manual start operation; the specifics are not limited here.

[0109] 202. Based on the closing request, create a closing task list belonging to the target business segment within the target time period, wherein the closing task list includes multiple closing tasks from multiple closing organizations.

[0110] The target time period described in this application embodiment can be a year, half a year, a quarter, a month, etc. Generally, any time period with a substantial time span can be used as the unit of the target time period. Furthermore, the target business segment can be a classification based on business type, for example, the target business segment can be classified according to business types such as logistics, construction, and finance. The closing task list is interconnected with its multiple closing organizations; that is, each closing task in the closing task list is required and can be executed by the multiple closing organizations, and is not associated with other closing organizations that do not need to execute any closing tasks.

[0111] The closing task requests can be divided into different types of closing task requests. Different types of closing tasks require different financial data. For example, closing task requests can be divided into logistics-type closing task requests, construction-type closing task requests, financial-type closing task requests, etc., depending on the specific closing task request.

[0112] After identifying the target business segment, it is also possible to identify the multiple accounting organizations included under that segment; these organizations can be companies, units, groups, etc. For example, assuming the target business segment is identified as the logistics segment, the various logistics companies under the logistics segment can be obtained, and these logistics companies are the target organizations under their respective segments. Of course, the segment can also be other types of segments, which are not limited here.

[0113] 203. Publish the closing task list to the plurality of closing organizations, so that each of the plurality of closing organizations executes the closing tasks associated with itself in the closing task list.

[0114] In this step, the closing task list can be sent to the multiple closing organizations via a local area network or via the Internet. The task list can be sent directly to the multiple closing organizations themselves, or directly to a business operating system or a business platform. The multiple closing organizations can log in to the business operating system or business platform through authorized login to view the closing task list, enabling the multiple closing organizations to execute the corresponding closing tasks according to the closing task list.

[0115] The task list can be a preset task list or a task list determined manually in real time. If a preset task list is adopted, after obtaining each target organization, the preset task list for the logistics organization can be published to each logistics organization based on the specific target organization, such as a logistics organization. If a task list is determined manually in real time, after obtaining each target organization, the specific closing tasks in the closing task list can be determined manually based on the specific target organization, such as a logistics organization, and the closing task list can be published to each target organization.

[0116] 204. Obtain the completion status of each closing task in the closing task list executed by each closing organization.

[0117] After each target organization executes the closing tasks in the closing task list, the completion status of each closing task is obtained. The completion status can include completed, incomplete, etc., or a preliminary task list status can be determined based on the comprehensive task status of each closing task. For example, if there are 10 closing tasks in the task list and 8 closing tasks are completed, that is, the task completion rate is 80%, the preliminary status of the task list can be considered as the completed status. The 80% completion rate here is just an example, and the completion rate can be adjusted according to the actual specific situation.

[0118] Each closing task in the closing task list may include a note on its progress, whether it is completed or not.

[0119] Furthermore, in this embodiment of the application, a completion result of the closing task list can be generated based on the completion status of each closing task. This completion result can be used to summarize the entire closing task, show the progress of each organization in key tasks, identify whether the task is delayed and the reasons for the delay, etc. For example, details of each closing task and the completion time of each closing task can be viewed. By comprehensively viewing the detailed information of each closing task, it can be used to predict risks or provide management insights for future new closing tasks.

[0120] For example, the completion results of the closing task list may include four tables:

[0121] (1) Task completion table, which may include task progress information, and if there are delays in the task progress information, it may also include the reasons for the delays.

[0122] (2) Task execution details table, which can query all tasks.

[0123] (3) Task process monitoring table, which can query the time nodes of all task completion.

[0124] (4) Task progress monitoring table, which can integrate and display the results of the generated task completion table, the generated task execution details table and the generated task process monitoring table.

[0125] This application sends a unified task list to different target organizations, enabling them to complete the execution and operation of related tasks on a unified task template. This allows managers to manage different organizations through a unified process system, improving efficiency compared to managing different process systems. Furthermore, executing task management on a unified task management system allows managers to access all task execution details, increasing transparency. After task execution is completed, results are generated, allowing managers to track the completion status of all tasks and control process risks.

[0126] like Figure 3 As shown, in some embodiments of this application, before obtaining the closing task request of the target closing organization within the target business segment and the target time period, the method further includes the following steps 301-302:

[0127] 301. Define closing task master data to represent each closing task, wherein the closing task master data includes information about the closing organization, information about the business segment to which the closing task belongs, and information about the source of the closing task.

[0128] The information about the closing organization can be its basic information, including its main business information such as its name, address, and operating information, including the business areas it operates in. The information about its business segments can be based on functional areas, such as construction, logistics, and finance. The information about the source of the closing task can be the closing task requests issued by the aforementioned segments.

[0129] For example, the specific information of the closing organization, the information of the business segment to which it belongs, and the information of the source of the closing task can be defined in the form of codes. When defining the closing organization, it can be defined which district the closing organization is located in. The district can be an administrative region, such as a city, a district under a city, or a street, etc. When defining the district information, the district code and the basic information description of the district can be defined by coding.

[0130] In addition, when defining the closing organization, regional information can also be defined. The region can be an administrative region such as the East Region, West Region, South Region, North Region, etc., or it can be a larger area. For example, according to national territory, it can be the Northwest Region, Southwest Region, Central Region, Northeast Region, South China Region, etc. There is no specific limitation. When defining the regional information, the regional code and description of the basic information of the region can be defined by encoding.

[0131] Furthermore, when defining the business segment, the segment code, segment description, etc., can also be defined through coding.

[0132] Furthermore, when defining specific closing organizations, the organization code and related descriptions can also be defined in the same way as described above.

[0133] Finally, the code for all master data can be used to make judgments. When the code determines that the organizational information, sector information, and source information match, the three can be associated. Among them, if the matching is performed according to the code, there are three matching methods:

[0134] (1) For example, direct matching is performed according to the section code and the code of the closing task request. When the two are exactly the same, the matching is completed.

[0135] (2) Alternatively, partial matching can be performed according to the code of the section and the code of the closing task request. For example, the first characters of the two codes are fixed characters. For example, when English letters are used for encoding, such as AB, HB, WL, etc., are used as the first code. When the first code matches, the match is successful.

[0136] (3) Alternatively, other matching mechanisms can be established to match the code of the board and the code of the closing task request with other encryption methods, such as designing corresponding encryption passwords. When the two passwords match, the matching is complete.

[0137] When the closing task request is met, including relevant organizational information, sector information, closing task source information, and other related information, the corresponding permission group code can also be added through this code.

[0138] It should be noted that the above embodiments only illustrate one way of doing this step. It is understood that the matching of the information mentioned above is not limited to matching through code. No specific method is specified here.

[0139] 302. When a request to create a closing task is obtained, a closing task is created based on the closing task master data.

[0140] By associating the closing task master data defined in step 301 above with the closing organization, target business segment, and closing task request source, a corresponding closing task can be created. For example, assuming that the closing task request obtained in the above embodiment is from the logistics segment, it can be determined that the closing task information originates from the logistics segment, and at the same time, the relevant logistics organization under the logistics segment can be obtained. Through the association of these three, a closing task related to the logistics organization can be created, rather than a closing task for a financial organization or a construction organization.

[0141] The tasks can be created manually based on the financial data required by the logistics organization, or by pre-setting the closing tasks of the logistics organization and directly obtaining a pre-set closing task template.

[0142] like Figure 4 As shown, in some embodiments of this application, before obtaining the list of closing tasks belonging to the target business segment within the target time period according to the closing request, the method further includes the following steps 401 to 403:

[0143] 401. Define the coding strategy for closing tasks.

[0144] As can be seen from step 302 of the above embodiment, if a pre-set closing task template is obtained, each pre-set closing task needs to be encoded. Encoding requires a coding strategy. The coding strategy can be manually standardized or randomly generated by a computer. The coding strategy can be any known coding strategy, and no specific limitation is made here.

[0145] 402. Encode the preset types of closing tasks according to the closing task coding strategy to obtain the closing task codes for each type.

[0146] When adopting a customized coding strategy, the coding strategy can be as follows: When dealing with specific closing tasks, uppercase English letters can be used as the beginning part of the code. For example, AA can be used for asset-type tasks, GL for general ledger-type tasks, MM for material-type tasks, TR for cash-type tasks, CO for management ledger-type tasks, AR for accounts receivable-type transactions, and AP for accounts payable-type transactions. Based on the initial English letter, an additional four digits can be added after the letter, for example, 12. 34, etc., where the scalability of the encoding can also be considered. When additional tasks of the same type need to be added, additional encodings can be added. For example, the last four digits of the encoding between two task items can differ by 10. For example, the difference between task AA1234 and task AA1224 is 10. When an additional task needs to be inserted, encoding AA1225 can be used as the encoding for the additional task. It should be noted that the encoding method of the first two English letters plus the last four Roman numerals is not the only encoding method, and this 6-digit encoding method can be extended to a maximum of 12 digits, such as AA0123456789.

[0147] When encoding according to the above method, Roman numerals can also represent different meanings. For example, if the task is AA0123456789, different Roman numerals will have different meanings. For instance, the single digit 9 can represent: task number, task description, task type, source system, permission group, program name, program variant, job name, offset days, planned start time, planned duration, task priority, task attribute, applicable sector, critical task, tax-related, and taxpayer attribute. Of course, the tens digit 8 can also represent any of the meanings mentioned above. Similarly, other Roman numerals can also represent any of the meanings mentioned above. In practice, adjustments can be made according to specific needs, and no specific restrictions are imposed here.

[0148] Each of the pre-coded tasks can be placed in a custom folder. The custom folder is an encrypted storage medium used to manage the pre-coded tasks. When a task needs to be retrieved, it must be decrypted by means of decryption, such as entering a password or other types of decryption, before the task can be retrieved.

[0149] 403. Define the closing task templates for each business segment by using various types of closing task codes, and obtain the closing task templates for each business segment.

[0150] Based on the pre-coded closing tasks, after determining the business segment to be executed, such as the logistics business segment, the specific closing tasks related to logistics that need to be called in the logistics business segment are filtered out according to the codes and combined into a task template. The task template includes at least one closing task related to logistics.

[0151] like Figure 5 As shown, in some embodiments of this application, the method of creating a list of closing tasks belonging to the target business segment within the target time period based on the closing request may further include the following steps 501-502:

[0152] 501. Through the multiple closing organizations and the multiple closing tasks, set closing organization permissions for each closing task corresponding to each target closing organization, wherein the closing organization permissions include browsing permissions and operation permissions of the closing organization.

[0153] When obtaining the closing task list, permissions can be set for the task templates mentioned in the above embodiments in combination with those of each closing organization. For example, assuming that the task templates under the logistics sector are obtained according to the above embodiments, and the number of logistics organizations under the logistics sector is also obtained, the two data are combined to perform corresponding permission encoding, so that when each organization executes closing tasks in the closing task list, it can only browse and operate the closing tasks under its own organization.

[0154] For example, if there are three closing tasks A, B, and C under the task template in the logistics section, and the logistics organizations under the logistics section are a, b, and c, then nine closing tasks can be obtained based on the data from both: Aa, Ab, Ac, Ba, Bb, Bc, Ca, Cb, and Cc. This means that logistics company A can only view and operate three closing tasks: Aa, Ba, and Ca; company B can only view and operate three closing tasks: Ab, Bb, and Cb; and company C can only view and operate three closing tasks: Ac, Bc, and Cc.

[0155] 502. Obtain the list of closing tasks based on the browsing permissions and the operation permissions.

[0156] After adding the browsing and operation permissions defined in section 501 to each closing task in the closing task list, you can obtain the closing task list with the added permissions.

[0157] In this context, after the closing task list is published to each closing organization, the number of closing tasks in the closing task list can also be added or deleted.

[0158] like Figure 6As shown, in some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method further includes the following steps 601-602:

[0159] 601. Determine the completion status of each closing task in the closing task list.

[0160] The closing task status mentioned in this step refers to the current task status of each closing task in the task list, or the task completion status.

[0161] For example, the task status can be: completed without errors, meaning the task has been executed normally and completed; completed with warnings, meaning the task has been completed but there is a warning message, which does not affect the actual completion; completed with errors, meaning the task has been executed but the returned execution result is an error, requiring the task to be executed again; or checked, meaning the task has been completed normally and the check has been completed. It should be noted that the task status mentioned in this embodiment is only one way and does not limit the definition of other task statuses.

[0162] 602. Based on the completion status of each closing task, determine the completion status of the target closing organization in executing the closing task list.

[0163] The status of the closing task list is determined by the completion status of each closing task in the closing task list. For example, if more than 90% of the tasks in the closing task list have been completed, then the closing task list can be determined to be completed. The 90% threshold can be adjusted, for example, it can be adjusted to 100%, that is, the closing task list is considered complete only when all the closing tasks in the closing task list have been completed.

[0164] If it is necessary to determine the list of closing tasks, it can also be determined through other methods, such as:

[0165] If at least one closing task in the closing task list has been completed, the closing task list is determined to be in an active state; for example, the active state can be represented by the letter A.

[0166] If all tasks in the closing task list have been completed, the closing task list is determined to be in a completed state; for example, the active state can be represented by the letter F.

[0167] If the current task in the closing task list is in a paused state, the closing task list is determined to be in a paused state; for example, the active state can be represented by the letter L.

[0168] If the closing task list is not published to the target closing organization after it is created, the closing task list is determined to be in an unpublished state; for example, the active state can be represented by the letter N.

[0169] If the closing task list has been created and published to the target closing organization, the closing task list is determined to be in a published state; for example, the active state can be represented by the letter X.

[0170] In some embodiments of this application, after determining the completion status of the target closing organization's execution of the closing task list based on the completion status of each closing task, the method further includes:

[0171] If the closing task list is active or published, check the status of the currently executing closing tasks in the closing task list according to a preset period and update the completion status of the closing task list.

[0172] After the closing task list is published, each closing organization begins to execute the closing tasks in the list. As each closing organization executes a task, the task status will change. For example, when a unit of time, including a working day, has elapsed, the task is completed by the closing organization, and the task status changes from uncompleted to completed. At this time, the task status needs to be updated.

[0173] The step of checking the status of currently executing closing tasks in the closing task list according to a preset period includes:

[0174] The task status of each closing task in the closing task list is obtained according to a preset cycle.

[0175] The current closing tasks are determined by checking the list of currently executing closing tasks at preset intervals, and include the following types:

[0176] 1) If the current closing task is being processed, determine the task status of the current closing task as "processing";

[0177] 2) If the current closing task has not yet started processing, determine the task status of the current closing task as unprocessed;

[0178] 3) If the current closing task has been completed without errors, determine the task status of the current closing task as completed and error-free.

[0179] 4) If the current closing task has been completed but there is a warning message, and this does not affect the actual completion, then the task status of the current closing task is determined to be "completed with warning".

[0180] 5) If the current closing task has been completed, but the returned execution result is an error, and the closing task needs to be executed again in the future, the task status of the current closing task should be determined to be "completed but error exists".

[0181] 6) If the current closing task has been checked and completed normally, the task status of the current closing task is set to "checked".

[0182] Based on the task status, update the completion status of the target closing organization in executing the closing task list.

[0183] The task status of the closing task can be determined manually based on the task status shown above, or it can be determined through other computer software or systems.

[0184] For example, once the task status can be determined, the SAP (systems applications and products in data processing) system can be used to periodically scan and execute the task. The task completion status can be manually confirmed and the task status can be modified. In addition, the system can also automatically distribute tasks to the SAP system for execution based on task dependencies or timed configurations. After execution, the system will automatically update the task status. For example, when a job-type task is completed, the task status can be checked through the transaction code, for example, the task code ZFI525, and synchronized to the SAP accounting system.

[0185] The SAP system proposed in this implementation is: SAP system, also known as enterprise management solution, whose function is to customize and create management systems for enterprises through software programs, and to supervise, analyze and manage all business activities and links of enterprises, including human resources, logistics and transportation, sales and service, transaction payment, product specifications and quality, production activities, raw material procurement, goods warehousing and inventory management, forming a data-driven resource management system, providing guidance and basis for enterprise production, decision-making and organizational operation, which is conducive to improving the quality of enterprise financial management and the rational allocation of enterprise funds.

[0186] It should be noted that using the SAP system is only one embodiment of this application and does not limit other methods.

[0187] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method may further include:

[0188] If the task status needs to be changed, then change the task status.

[0189] When the closing task list is closed, if the tasks in the closing task list still need to be updated, for example, if an error occurs during the execution of a task in the closing task list after the closing task list is closed, resulting in an unexpected result that needs to be re-executed, the task status can be changed by establishing a strategy.

[0190] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method further includes the following strategy:

[0191] (1) If the task status of the pre-closing task is the completed without error status, the completed with warning status, or the checked status, the post-closing task can change the task status when a task status change request is obtained.

[0192] In this embodiment, the prerequisite task is a necessary condition for the subsequent task; that is, the subsequent task can only be executed after the prerequisite task is completed. Specifically, if the current state of the subsequent task is incomplete when the prerequisite task is completed, the state can only be changed to a completed state after the subsequent task is executed.

[0193] (2) If the task status of the pre-closing task is the "processing" status or the "completed but errored" status, the post-closing task cannot change the task status when a task status change request is obtained.

[0194] The pre-tasks and post-tasks described in this strategy are the same as before. When the pre-task is in an incomplete state, the post-task cannot be started. Therefore, even if the post-task has been executed by the corresponding closing task organization, the task status of the post-task cannot be changed from incomplete to not completed.

[0195] (3) If the task status of the preceding task changes when the subsequent closing task has been completed, the task status of the subsequent closing task automatically changes to the completed but error-prone state when a task status change request is obtained.

[0196] If the preceding task and the following task are both completed, and the preceding task needs to change its status for special reasons, such as changing from a completed state to an incomplete state, the situation is similar to the strategy in point (2) of this application embodiment. That is, the preceding task is incomplete, so the following task should be in an incomplete state. However, the completion result of the following task has been uploaded, so the status of the following task will change to a completed state with an error.

[0197] (4) If the task status of the pre-closing task is completed without errors or checked, prompt whether the post-closing task should start immediately. If the information is yes, start the post-closing task. If the information is no, end the execution of the post-closing task.

[0198] When the task status is changed, the reason for the change can be entered for easy query later. When the task status is changed to completed, error-free or checked, after confirmation, a prompt will appear asking whether to plan the next task to start immediately. If yes is selected, the task will be sent to the SAP system; otherwise, the process will end.

[0199] When executing a closing task list using the SAP system, exceeding the planned duration of a closing task will not affect actual execution; the task can still be executed on the platform even if the planned duration is exceeded. If there are job-related tasks in the closing task list, they will run automatically, but only once, and cannot detect new data. For example, in the GR / IR reclassification SSP, after the system completes the execution without errors, the status will display a green light, and even if new data is received from the front end, the task status in the system will not change.

[0200] The GR / IR mentioned above stands for Goods Receipt / Invoice Receipt. In the SAP system, GR / IR is a transitional account used to record goods in transit and accounts payable, with the purpose of obtaining financial statements.

[0201] The SAP system separates the receiving and invoice verification and posting processes into two departments. The receiving action is called GR, which is an inventory posting action performed by the warehouse, debiting inventory and crediting the transition account. When the invoice is received, the finance department performs the invoice verification and posting action, debiting the transition account and crediting accounts payable. In this way, the transition between the debit and credit sides is cleared.

[0202] The aforementioned SSP (Supply Side Platform) allows publishers to participate in ad transactions, making their inventory of ads available. Through this platform, vendors aim to achieve the highest effective cost per thousand impressions (CPM) for their inventory ads, rather than selling them at a low price.

[0203] like Figure 7 As shown, in some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the method may further include the following steps 701-704:

[0204] 701. When the completion status of each actual closing task in the closing task list is consistent with the current completion status of each closing task, the execution of the closing task list ends.

[0205] 702. When the current completion status of at least one closing task is inconsistent with the actual closing completion status, prompt whether to complete the closing task list.

[0206] When a user selects the corresponding closing task list and clicks to close the task list, the task list will be changed to "completed". If there are still unfinished tasks, but these unfinished tasks have not been sent to the SAP system, the user will be prompted that there are still unfinished items in the task list.

[0207] 703. If the user selects "yes", the execution of the closing task list will end.

[0208] The closed list of closing tasks can be reopened by clicking "Reopen". After reopening, the closing tasks can be executed again. Once the adjustments are completed, click "Close Task List" again to complete the closed loop of the closing process. When the closing task list is closed, the scanning program will stop scanning the closing task list.

[0209] 704. If the user selects "no", continue executing the closing task list.

[0210] like Figure 8 As shown, in some embodiments of this application, a method for cross-organizational closing task management is also provided, the method comprising the following steps 801-804:

[0211] 801. Obtain multiple closing requests from the target closing organization during the second target time period.

[0212] This step can obtain multiple closing requests at the same time. The rest is the same as step 201 above, so it will not be repeated here.

[0213] 802. Based on the multiple closing requests, create a list of closing tasks belonging to each business segment within the second target time period, wherein each closing task list includes multiple closing tasks of multiple target closing organizations.

[0214] This step allows for the simultaneous execution of multiple closing tasks. Multiple closing task lists can be created and executed simultaneously based on different target sectors and target organizations. Other aspects are the same as in step 202 above, so they will not be repeated here.

[0215] 803. Publish the various closing task lists to the multiple target closing organizations, so that the multiple target closing organizations execute the closing tasks associated with themselves in the closing task lists associated with themselves.

[0216] In this step, multiple target closing organizations can simultaneously execute related tasks in different closing task lists. The rest is the same as in step 203 above, so it will not be repeated here.

[0217] 804. Obtain the completion status of each closing task in the closing task list associated with the multiple target closing organizations.

[0218] This step allows us to obtain the completion status of each closing task in multiple closing task lists. The rest is the same as in step 204 above, so it will not be repeated here.

[0219] To better implement the cross-organizational task management method in the embodiments of this application, in addition to cross-organizational task management, the embodiments of this application also provide a cross-organizational task management device, such as... Figure 9 As shown, the cross-organizational task management device 900 includes:

[0220] The first acquisition module 901 is used to acquire the closing request of the target closing organization within the target business segment and the target time period.

[0221] The creation module 902 is used to create a list of closing tasks belonging to the target business segment within the target time period according to the closing request. The list of closing tasks includes multiple closing tasks of multiple closing organizations.

[0222] The publishing module 903 is used to publish the closing task list to the multiple closing organizations, so that each closing organization executes the closing tasks associated with itself in the closing task list;

[0223] The second acquisition module 904 is used to acquire the completion status of each closing task in the closing task list executed by each closing organization.

[0224] This application, through the first acquisition module 901 and the creation module 902, sends a unified task list to different target organizations after obtaining the closing request, via the publishing module 903. This allows different target organizations to complete the execution and operation of relevant tasks on a unified task template. The completion status of each closing task is obtained through the second acquisition module 904, enabling managers to manage different organizations through a unified process system, which improves efficiency compared to managing different process systems. At the same time, performing task management on a unified task management system allows managers to obtain all task execution details, improving the transparency of task execution. After the management task execution is completed, the task execution results can also be generated, allowing managers to statistically analyze the completion status of all tasks and control process risks.

[0225] In some embodiments of this application, the first acquisition module is specifically used for:

[0226] Retrieve the closing requests of the target closing organization within the target business segment and the target time period.

[0227] In some embodiments of this application, before obtaining the list of closing tasks belonging to the target business segment within the target time period according to the closing request;

[0228] The first acquisition module is specifically used for:

[0229] By coding each closing task, the closing task template corresponding to the business segment is defined, and the corresponding closing task template is obtained.

[0230] In some embodiments of this application, the step of creating a list of closing tasks belonging to the target business segment within the target time period according to the closing request, wherein the list of closing tasks includes multiple closing tasks of multiple closing organizations;

[0231] The creation module is specifically used for:

[0232] Based on the browsing permissions and operation permissions, obtain the list of closing tasks.

[0233] In some embodiments of this application, after obtaining the completion status of each closing task in the closing task list executed by each closing organization, the second obtaining module is specifically used for:

[0234] Determine the completion status of each closing task in the closing task list;

[0235] Based on the completion status of each closing task, the completion status of the target closing organization in executing the closing task list is determined.

[0236] In some embodiments of this application, the step of checking the currently executing closing tasks in the closing task list according to a preset period is described.

[0237] The second acquisition module is also specifically used for:

[0238] The task status of each closing task in the closing task list is obtained according to a preset cycle.

[0239] This application embodiment also provides a cross-organizational task management device, which integrates any of the cross-organizational task management devices provided in this application embodiment, the cross-organizational task management device comprising:

[0240] One or more processors;

[0241] Memory; and

[0242] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps in cross-organizational task management as described in any of the embodiments.

[0243] This application also provides a cross-organizational task management device that integrates any of the cross-organizational task management methods provided in this application, such as... Figure 10 As shown, it illustrates a structural schematic diagram of the cross-organizational task management device involved in the embodiments of this application. Specifically:

[0244] This cross-organizational task management device may include components such as a processor 1001 with one or more processing cores, a memory 1002 with one or more computer-readable storage media, a power supply 1003, and an input unit 1004. Those skilled in the art will understand that... Figure 10 The cross-organizational task management device structure shown does not constitute a limitation on cross-organizational task management devices and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0245] The processor 1001 is the control center of the cross-organizational task management device. It connects various parts of the device via various interfaces and lines, and executes software programs and / or modules stored in the memory 1002, as well as calling data stored in the memory 1002, to perform various functions and process data, thereby providing overall monitoring of the device. Optionally, the processor 1001 may include one or more processing cores. The processor 1001 may be a Central Processing Unit (CPU), or 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. Preferably, the processor 1001 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understandable that the aforementioned modem processor may not be integrated into processor 1001.

[0246] The memory 1002 can be used to store software programs and modules. The processor 1001 executes various functional applications and data processing by running the software programs and modules stored in the memory 1002. The memory 1002 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created based on the use of cross-organizational task management devices, etc. In addition, the memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 1002 may also include a memory controller to provide the processor 1001 with access to the memory 1002.

[0247] The cross-organizational task management device also includes a power supply 1003 that supplies power to various components. Preferably, the power supply 1003 can be logically connected to the processor 1001 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 1003 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0248] The cross-organizational task management device may also include an input unit 1004, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0249] Although not shown, the cross-organizational task management device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 1001 in the cross-organizational task management device loads the executable files corresponding to the processes of one or more applications into the memory 1002 according to the following instructions, and the processor 1001 runs the applications stored in the memory 1002 to realize various functions, such as:

[0250] Obtain the closing requests from the target closing organization within the target business segment and for the target time period;

[0251] Based on the closing request, a closing task list belonging to the target business segment within the target time period is created, and the closing task list includes multiple closing tasks from multiple closing organizations.

[0252] The closing task list is published to the plurality of closing organizations, so that each of the plurality of closing organizations executes the closing tasks associated with itself in the closing task list;

[0253] Obtain the completion status of each closing task in the closing task list executed by each closing organization.

[0254] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0255] Therefore, embodiments of this application provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a disk, or an optical disk, etc. A computer program is stored thereon, which is loaded by a processor to execute the steps of any of the cross-organizational task management methods provided in embodiments of this application. For example, the computer program loaded by the processor can execute the following steps:

[0256] Obtain the closing requests from the target closing organization within the target business segment and for the target time period;

[0257] Based on the closing request, a closing task list belonging to the target business segment within the target time period is created, and the closing task list includes multiple closing tasks from multiple closing organizations.

[0258] The closing task list is published to the plurality of closing organizations, so that each of the plurality of closing organizations executes the closing tasks associated with itself in the closing task list;

[0259] Obtain the completion status of each closing task in the closing task list executed by each closing organization.

[0260] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the detailed descriptions of other embodiments above, which will not be repeated here.

[0261] In practice, each of the above units or structures can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units or structures, please refer to the previous method embodiments, which will not be repeated here.

[0262] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0263] The foregoing has provided a detailed description of a cross-organizational task management method and apparatus provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A cross-organizational account task management method, characterized by, The method comprises the following steps: obtaining a target account closing organization's account closing request in a target business board and a target time period; setting an account closing organization permission corresponding to the target account closing organization for each account closing task through a plurality of account closing organizations and a plurality of account closing tasks of the plurality of account closing organizations, wherein the account closing organization permission comprises a browsing permission of the account closing organization and an operation permission of the account closing organization, and the account closing organization comprises at least one of the following organizations: a company, a unit or a group; creating an account closing task list according to the browsing permission and the operation permission, wherein the account closing task list comprises a plurality of account closing tasks of the plurality of account closing organizations; publishing the account closing task list to the plurality of account closing organizations, so that each account closing organization of the plurality of account closing organizations executes an account closing task associated with itself in the account closing task list; obtaining a completion state of each account closing task executed by each account closing organization in the account closing task list; determining the completion state of each account closing task in the account closing task list; determining a completion state of the account closing task list executed by the target account closing organization according to the completion state of each account closing task; the completion state of the account closing task list comprises an active state, a completed state, a suspended state, an unpublished state or a published state.

2. The cross-organization account closing task management method according to claim 1, wherein before the step of obtaining the target account closing organization's account closing task request in the target business board and the target time period, the method further comprises: defining an account closing task master data for representing each account closing task, wherein the account closing task master data comprises information of an account closing organization, information of a business board to which an account closing task belongs and information of a source of the account closing task; when obtaining the account closing task request, creating an account closing task according to the account closing task master data.

3. The cross-organizational account task management method of claim 1, wherein, before the step of obtaining the account closing task list belonging to the target business board in the target time period according to the account closing request, the method further comprises: defining an account closing task coding strategy; coding various types of account closing tasks according to the account closing task coding strategy to obtain various types of account closing task codes; defining an account closing task template corresponding to each business board through various types of account closing task codes to obtain an account closing task template corresponding to each business board.

4. The cross-organ account task management method of claim 1, wherein, the step of determining the completion state of the account closing task list executed by the target account closing organization according to the completion state of each account closing task comprises: if at least one account closing task in the account closing task list has been completed, determining that the account closing task list is in an active state; if all tasks in the account closing task list have been completed, determining that the account closing task list is in a completed state; if a current task in the account closing task list is in a suspended state, determining that the account closing task list is in a suspended state; if the account closing task list has not been published to the target account closing organization after being created, determining that the account closing task list is in an unpublished state; if the account closing task list has been published to the target account closing organization after being created, determining that the account closing task list is in a published state.

5. The cross-organ account task management method of claim 1, wherein, After the completion state of the target account closing organization executing the account closing task list is determined according to the completion state of each account closing task, the method further comprises: If the account closing task list is in an active state or an issued state, the current execution state of the account closing task in the account closing task list is checked according to a preset period, and the completion state of the account closing task list is updated.

6. The cross-organ account task management method of claim 5, wherein, The current execution state of the account closing task in the account closing task list is checked according to a preset period, and the completion state of the account closing task list is updated. The task state of each account closing task in the account closing task list is acquired according to a preset period; The completion state of the target account closing organization executing the account closing task list is updated according to the task state.

7. The cross-organ account task management method of claim 6, wherein, The task state of each account closing task in the account closing task list is acquired according to a preset period, and the completion state of the account closing task list is updated. If the current account closing task is being processed, the task state of the current account closing task is determined as a processing state; If the current account closing task is not being processed, the task state of the current account closing task is determined as an unprocessed state; If the current account closing task has been completed and there is no error, the task state of the current account closing task is determined as a completed and error-free state; If the current account closing task has been completed, but there is a warning message, and the actual completion is not affected, the task state of the current account closing task is determined as a completed and warning state; If the current account closing task has been completed, but the returned execution result is an error, and the account closing task needs to be executed again subsequently, the task state of the current account closing task is determined as a completed and error state; If the current account closing task has been completed and checked, and has been normally completed, the task state of the current account closing task is determined as a checked state.

8. The cross-organ account task management method of claim 7, wherein, After the completion state of each account closing task executed by each account closing organization in the account closing task list is acquired, the method further comprises: If the task state of the preceding account closing task is the completed and error-free state, the completed and warning state, or the checked state, and a task state change request is acquired, the task state of the subsequent account closing task is changed; If the task state of the preceding account closing task is the processing state or the completed and error state, and a task state change request is acquired, the task state of the subsequent account closing task cannot be changed; If the task state of the preceding account closing task is changed when the subsequent account closing task has been completed, and a task state change request is acquired, the task state of the subsequent account closing task is automatically changed to the completed and error state; If the task state of the preceding account closing task is the completed and error-free state or the checked state, whether the subsequent account closing task is immediately started is prompted, when information that the subsequent account closing task is started is acquired, the subsequent account closing task is started, and when information that the subsequent account closing task is not started is acquired, the execution of the subsequent account closing task is ended.

9. The cross-organ account task management method of claim 1, wherein, After the completion state of each account closing task executed by each account closing organization in the account closing task list is acquired, the method further comprises: When the completion state of each actual account closing task in the account closing task list is consistent with the current completion state of each account closing task, the execution of the account closing task list is ended. When the current completion status of at least one account closing task is inconsistent with the actual account closing completion status, prompting whether to complete the account closing task list; If the information that the user selects is yes is obtained, ending the execution of the account closing task list; If the information that the user selects is no is obtained, continuing to execute the account closing task list.

10. A cross-organizational task management apparatus characterized by comprising: Comprise: The first acquisition module is used for acquiring the account closing request of the target account closing organization in the target time period under the target business board; The creation module is used for setting the account closing organization permission corresponding to each account closing task for the target account closing organization through a plurality of account closing organizations and a plurality of account closing tasks of the plurality of account closing organizations, the account closing organization permission comprising the account closing organization browsing permission and the account closing organization operation permission; the account closing organization comprises at least one of the following organizations: company, unit or group; according to the browsing permission and the operation permission, an account closing task list is created, and the account closing task list comprises a plurality of account closing tasks of a plurality of account closing organizations; The publishing module is used for publishing the account closing task list to the plurality of account closing organizations, so that each account closing organization executes the account closing task associated with itself in the account closing task list; The second acquisition module is used for acquiring the completion status of each account closing task executed by each account closing organization in the account closing task list; The completion status of each account closing task in the account closing task list is determined; According to the completion status of each account closing task, the completion status of the target account closing organization executing the account closing task list is determined; The completion status of the account closing task list comprises: active state, completion state, pause state, non-published state, or published state.

11. A cross-organizational task management device, comprising: one or more processors; a memory; and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the cross-organizational account closing task management method of any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a plurality of instructions adapted to be loaded by the processor to execute the steps in the cross-organizational account closing task management method of any one of claims 1 to 9.

Images