CN115082000A

CN115082000A - Cross-organization account closing task management method, device, equipment and storage medium

Info

Publication number: CN115082000A
Application number: CN202110268524.9A
Authority: CN
Inventors: 朱燕
Original assignee: SF Technology Co Ltd
Current assignee: SF Technology Co Ltd
Priority date: 2021-03-12
Filing date: 2021-03-12
Publication date: 2022-09-20

Abstract

The application provides a cross-organization account clearance task management method, a device, equipment and a storage medium, wherein the cross-organization account clearance task management method comprises the following steps: acquiring a clearance request of a target clearance organization in a target time period under a target service plate; acquiring a clearance task list belonging to a target service plate in a target time period according to the clearance request, wherein the clearance task list comprises a plurality of clearance tasks organized by a plurality of clearances; issuing the account clearance task list to a plurality of account clearance organizations, so that each account clearance organization in the plurality of account clearance organizations executes the account clearance task associated with the account clearance task list; and acquiring the completion state of each account clearance task in each account clearance organization execution account clearance task list. The method and the system can provide the unified task list for different organizations, so that the different organizations complete respective corresponding tasks under the unified task list, a manager can realize cross-organization task management in a unified management system, and the management efficiency is improved.

Description

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

Technical Field

The application relates to the field of informatization software, in particular to a cross-organization account clearance task management method, a device, equipment and a storage medium.

Background

With the development of information technology, the process management of information automation is applied more and more widely in different companies, however, different companies often have their own unique process management methods and systems, and when it is necessary to perform unified process management on different companies or target account-related organizations, the unified process management is lacking, and the following problems occur:

the method has the advantages that many process management systems lack unified control, different process system process butt joint modes are different, the processes are not smooth when unified, or manual management is used, when manual management is used, different process management pages still need to be logged in, so that the operation smoothness is affected, and a scene that results are wrong due to manual data input errors caused by manual execution exists.

The information transmission is not accurate, when the flow system is too much and cannot be unified, manual flow operation is sometimes changed, the offline mail is sent to different executives, the mail transmission mode is influenced by the accuracy of the mail address, the post movement of the staff and the like, and the situations of information transmission failure in time or transmission errors occur.

The execution process is opaque, different process management systems correspond to the operations of different executors, the progress condition and progress of the task have no effective visual management work, and managers cannot check the progress and identify possible risk points at any time.

Therefore, how to perform unified task flow management on different companies becomes a technical problem to be solved.

Disclosure of Invention

The application provides a cross-organization customs clearance task management method, which enables different organizations to complete respective corresponding tasks under a unified task list by providing the unified task list for the different organizations, so that a manager can realize cross-organization task management in a unified standard management interface or management system, the manager is prevented from performing task management according to management modes or management systems of the different organizations, and the management efficiency is improved.

In one aspect, the present application provides a cross-organization customs clearance task management method, including:

acquiring a clearance request of a target clearance organization in a target time period under a target service plate;

according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period is created, wherein the account clearance task list comprises a plurality of account clearance tasks organized by a plurality of account clearances;

issuing the account clearance task list to the plurality of account clearance organizations, so that each account clearance organization in the plurality of account clearance organizations executes the account clearance task associated with the account clearance task list;

and acquiring the completion state of each account clearance task in the account clearance task list executed by each account clearance organization.

In some embodiments of the present application, before the obtaining a request for a tie-out task of a target tie-out organization in a target time period under a target business plate, the method further includes:

defining account clearance task main data used for representing each account clearance task, wherein the account clearance task main data comprises information of an account clearance organization, information of a business plate to which the account clearance task belongs and information of an account clearance task source;

and when acquiring a request for creating a ledger task, creating the ledger task according to the ledger task master data.

In some embodiments of the present application, before the obtaining, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period, the method further includes:

defining a customs account task coding strategy;

coding preset various types of account clearance tasks according to the account clearance task coding strategy to obtain various types of account clearance task codes;

and defining a account closing task template corresponding to each service plate through various types of account closing task codes to obtain the account closing task template corresponding to each service plate.

In some embodiments of the present application, the creating, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period includes:

setting a plurality of customs clearance organizations and a plurality of customs clearance tasks for each customs clearance task, wherein the customs clearance organization authority corresponds to each target customs clearance organization, and comprises a browsing authority of the customs clearance organization and an operation authority of the customs clearance organization;

and acquiring the account clearance task list according to the browsing permission and the operation permission.

In some embodiments of the present application, after obtaining a completion status of each ledger task in the ledger task list executed by each ledger organization, the method further includes:

determining the completion state of each account clearance task in the account clearance task list;

and determining the completion state of the target account clearance organization executing the account clearance task list according to the completion state of each account clearance task.

In some embodiments of the present application, the determining, according to the completion status of each of the customs clearance tasks, the completion status of the target customs clearance organization executing the customs clearance task list includes:

if at least one account clearance task in the account clearance task list is completed, determining that the account clearance task list is in an activated state;

if all tasks in the account clearance task list are finished, determining that the account clearance task list is in a finished state;

if the current task in the account clearance task list is in a pause state, determining that the account clearance task list is in the pause state;

if the account clearance task list is not issued to the target account clearance organization after the account clearance task list is established, determining that the account clearance task list is in an unpublished state;

and if the clearance task list is already published to the target clearance organization after the clearance task list is established, determining that the clearance task list is in a published state.

In some embodiments of the present application, after determining, according to the completion status of each of the customs clearance tasks, the completion status of the target customs clearance organization executing the customs clearance task list, the method further includes:

and if the account clearance task list is in an activated state or in a released state, checking the condition of the currently executed account clearance task in the account clearance task list according to a preset period, and updating the completion state of the account clearance task list.

In some embodiments of the present application, the checking, according to a preset period, a condition of a currently executed account clearance task in the account clearance task list includes:

acquiring the task state of each account clearance task in the account clearance task list according to a preset period;

and updating the completion state of the target account clearance organization for executing the account clearance task list according to the task state.

In some embodiments of the present application, the acquiring the task state of each account clearance task in the account clearance task list according to a preset period includes:

if the current account clearance task is being processed, determining the task state of the current account clearance task as the processing state;

if the current account clearance task does not start to be processed, determining that the task state of the current account clearance task is an unprocessed state;

if the current account clearance task is finished and has no error, determining the task state of the current account clearance task as a finished error-free state;

if the current account clearance task is finished but a warning message exists, and the actual completion is not influenced, determining that the task state of the current account clearance task is a finished warning state;

if the current account clearance task is finished, but the returned execution result is an error, and the account clearance task needs to be executed again subsequently, determining that the task state of the current account clearance task is a finished error state;

and if the current account clearance task is finished and normally finished, determining that the task state of the current account clearance task is the checked state.

In some embodiments of the present application, after obtaining a completion status of each ledger organization executing each ledger task in the ledger task list, the method further includes:

if the task state of the pre-account clearance task is the completed error-free state, the completed warning state or the checked state, the post-account clearance task can change the task state when a task state change request is acquired;

if the task state of the pre-account clearance task is the in-process state and the completed error state, the post-account clearance task cannot change the task state when a task state change request is acquired;

if the task state of the pre-customs clearance task is changed when the post-customs clearance task is finished, and the task state of the post-customs clearance task is automatically changed into the finished error state when a task state change request is acquired;

and if the task state of the front account clearance task is a finished error-free state and a checked state, prompting whether the rear account clearance task starts immediately, starting the rear account clearance task when the selected information is acquired, and finishing executing the rear account clearance task when the selected information is acquired.

In some embodiments of the present application, after obtaining the completion status of each ledger task executed by each ledger organization in the ledger task list, the method further includes:

when the completion state of each actual account clearance task in the account clearance task list is consistent with the current completion state of each account clearance task, finishing executing the account clearance task list;

when the current completion state of at least one account clearance task is inconsistent with the actual account clearance completion state, prompting whether the account clearance task list is completed or not;

if the information selected as yes by the user is acquired, finishing executing the account clearance task list;

and if the information selected by the user is not acquired, continuing to execute the account clearance task list.

In another aspect, the present application further provides a cross-organization customs clearance task management method, where the method includes:

acquiring a plurality of account clearance requests of a target account clearance organization in a second target time period;

creating each account closing task list belonging to each business plate in the second target time period according to the plurality of account closing requests, wherein each account closing task list comprises a plurality of account closing tasks organized by a plurality of target account closing;

issuing each account clearance task list to each target account clearance organization, so that each target account clearance organization executes the account clearance tasks related to the target account clearance organization in the account clearance task list related to the target account clearance organization;

and acquiring the completion state of each account closing task in the account closing task list which is associated with each target account closing organization and executed by each target account closing organization.

In another aspect, the present application further provides a cross-organization task management device, including:

the first acquisition module is used for acquiring a clearance request of a target clearance organization in a target time period under a target service plate;

the creating module is used for creating a customed account task list belonging to the target business plate in the target time period according to the customed account request, wherein the customed account task list comprises a plurality of customed account tasks organized by a plurality of customed account;

the issuing module is used for issuing the account clearance task lists to the plurality of account clearance organizations so that the account clearance organizations execute the account clearance tasks related to the account clearance task lists;

and the second acquisition module is used for acquiring the completion state of each account clearance task in the account clearance task list executed by each account clearance organization.

In some embodiments of the present application, the first obtaining module is specifically configured to:

and acquiring a clearance request of the target clearance organization in a target time period under the target service plate.

In some embodiments of the present application, before the acquiring, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period;

the first obtaining module is specifically configured to:

In some embodiments of the present application, the creating, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period, where the account clearance task list includes multiple account clearance tasks organized by multiple account clearances;

the creation module is specifically configured to:

In some embodiments of the present application, after the obtaining of the completion status of each ledger task in the ledger task list executed by each ledger organization, the second obtaining module is specifically configured to:

In some embodiments of the present application, the checking, according to a preset period, a condition of a current account clearance task in the account clearance task list;

the second obtaining module is specifically further configured to:

and acquiring the task state of each account clearance task in the account clearance task list according to a preset period.

In another aspect, the present application further provides a cross-organization task management device, where the cross-organization task management device includes:

one or more processors;

a memory; and

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 of the cross-organizational task management methods.

In another aspect, the present application further provides a computer-readable storage medium storing a plurality of instructions, the instructions being suitable for being loaded by a processor to perform any one of the steps of the cross-organization ledger task management method.

According to the method and the system, the unified task list is sent to different target organizations, so that the different target organizations can complete execution and operation of related tasks on the unified task template, a manager can manage different organizations through the unified flow system, and compared with the management of different flow systems, the efficiency is improved; meanwhile, task management is executed on a unified task management system, so that a manager can acquire execution details of all tasks, and the task execution transparency is improved; after the management task is completed, the result of task execution can be generated, so that a manager can count the completion conditions of all tasks and control the process risk.

Drawings

FIG. 1 is a schematic diagram of a scenario of a system for cross-organizational task management provided in an embodiment of the present application;

FIG. 2 is a flowchart illustrating an embodiment of a cross-organization task management method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of an embodiment of creating a customs clearance task in an embodiment of the application;

FIG. 4 is a flow diagram of one embodiment of obtaining a ledger task template in an embodiment of the present application;

FIG. 5 is a schematic diagram of one embodiment of step 202 in the embodiment of the present application;

FIG. 6 is a flowchart of one embodiment of determining a task status of a ledger task sheet in an embodiment of the present application;

FIG. 7 is a flow diagram illustrating one embodiment of closing a list of closed-account tasks, as described herein;

FIG. 8 is a structural diagram illustrating an embodiment of a cross-organization task management method according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of an embodiment of an apparatus for cross-organization task management according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an embodiment of an apparatus for cross-organization task management in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the description of the present application, it is to be understood that the terms "first", "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.

In this application, the word "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for the purpose of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known structures and processes are not set forth in detail in order to avoid obscuring the description of the present application with unnecessary detail. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

The present application provides a cross-organization task management method, apparatus, device and storage medium, which are described in detail below.

Referring to fig. 1, fig. 1 is a schematic view of a scene of a cross-organization task management method provided in an embodiment of the present application, where the cross-organization task management system may include a terminal device 100 and a background device 200, the terminal device 100 is in communication connection with the background device 200, the terminal device 100 may transmit data to the background device 200, and the background device 200 may also transmit data to the terminal device 100, such as the terminal device 100 in fig. 1, which may transmit the data to the background device 200 according to obtained real-time data; the background device 200 may calculate a scheme for cross-organization task management, and then transmit the scheme for cross-organization task management to the terminal device 100.

In the embodiment of the present application, the terminal device 100 includes, but is not limited to, a desktop, a portable computer, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, and the like.

In this embodiment of the present application, the background device 200 may be an independent server, or may be a server network or a server cluster composed of servers, for example, the device 200 for cross-organization task management described in this embodiment of the present application includes, but is not limited to, a computer, a network host, a single network server, multiple network server sets, or a cloud server composed of multiple servers. Among them, the Cloud server is constituted by a large number of computers or web servers based on Cloud Computing (Cloud Computing).

In the embodiment of the present application, the terminal device 100 and the backend device 200 may implement communication through any communication manner, including but not limited to mobile communication based on the third Generation Partnership Project (3 GPP), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), or computer network communication based on the TCP/IP Protocol Suite (TCP/IP), User Datagram Protocol (UDP), and the like.

It can be understood by those skilled in the art that the application environment shown in fig. 1 is only one application scenario related to the present application, and does not constitute a limitation on the application scenario of the present application, and that other application environments may further include more or less terminal devices and background devices than those shown in fig. 1, for example, only 1 terminal device or background device is shown in fig. 1, and the cross-organizational task management system may further include one or more other terminal devices and background devices that can process data, and are not limited herein.

In addition, as shown in fig. 1, the cross-organization task management system may further include a memory 300 for storing data, such as data of scheduling processes, scheduling results, and the like in the cross-organization task management.

It should be noted that the scenario diagram of the cross-organization task management system shown in fig. 1 is only an example, and the cross-organization task management system and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application.

As shown in fig. 2, fig. 2 is a schematic flowchart of an embodiment of a cross-organization task management method in the embodiment of the present application, where the cross-organization task management method may include the following steps 201 to 204:

201. and acquiring a clearance request of the target clearance organization in a target time period under the target service plate.

In this embodiment of the present application, a manner of obtaining the accounting request may be to directly obtain a computer instruction of the corresponding accounting request, or may also be to indirectly obtain a computer instruction of the corresponding accounting request from another memory, where the memory may be a general memory, or may also be a Cache memory, for example, a Cache memory, and it should be noted that obtaining the accounting request in this step is only a case of specific implementation, and a manner of obtaining the accounting request in another manner is not limited.

The account closing refers to an accounting function in unit time before a new account is enabled, the unit time of the target time period may be year, month, and the like, and after the account closing in unit time, tasks related to the accounting cannot be generally performed, for example: auditing, accounting, carrying out forward, and the like. The account clearance task request in this step is a pre-starting step for performing an account clearance task, where the account clearance task request may be a computer instruction or a manually performed starting operation, and is not limited herein.

202. And creating a clearance task list belonging to the target business plate in the target time period according to the clearance request, wherein the clearance task list comprises a plurality of clearance tasks organized by a plurality of clearances.

The target time period in the embodiment of the present application may be a period of one year, a half year, a quarter, a month, etc., and in general, a time having a substantial time span can be taken as a unit of the target time period. In addition, the target service plate may classify the service according to the service type, for example, the target service plate may be classified according to the service type of logistics, architecture, finance, and the like. The clearance task list is associated with a plurality of clearance organizations, namely, each clearance task in the clearance task list is needed and can be executed by the plurality of clearance organizations, and is not associated with other clearance organizations which do not need to execute each clearance task.

The account clearance task request can be divided into different types of account clearance task requests, the financial data required by the different types of account clearance tasks are different, for example, the account clearance task request can be divided into a logistics type account clearance task request, a building type account clearance task request, a financial type account clearance task request and the like, and the specific account clearance task request is determined.

After the target business plate is determined, a plurality of account clearance organizations included under the plate can be determined; the organization here may be a company, organization, group, etc. For example, if it is determined that the target service plate is a logistics plate, each logistics company under the logistics plate can be obtained according to the logistics plate, where each logistics company is each target organization under the corresponding plate, and the corresponding plate may also be other types of plates, which is not limited herein.

203. And issuing the account clearance task list to the plurality of account clearance organizations, so that each account clearance organization in the plurality of account clearance organizations executes the account clearance task associated with the account clearance task list.

In this step, the posting of the account clearance task list to the plurality of account clearance organizations may be sent in a local area network manner or in an internet manner, the task list may be directly sent to the plurality of account clearance organizations themselves or directly sent to one service operating system or one service platform, and the plurality of account clearance organizations may log in the service operating system or the service platform in an authority login manner and view the account clearance task list, so that the plurality of account clearance organizations may execute corresponding account clearance tasks according to the account clearance task list.

The task list can be a preset task list or a task list determined manually in time, and if the preset task list is adopted, after each target organization is obtained, the preset task list related to the logistics organization can be issued to each logistics organization according to a specific target organization, such as the logistics organization; if the task list is manually determined in time, after each target organization is obtained, the specific account clearance task in the account clearance task list can be manually determined according to the specific target organization, such as a logistics organization, and the account clearance task list is issued to each target organization.

204. And acquiring the completion state of each account clearance task in the account clearance task list executed by each account clearance organization.

After the target organizations execute the account-closing tasks in the account-closing task list, acquiring task completion conditions of the account-closing tasks, wherein the task completion conditions can include states of completed tasks, incomplete tasks and the like, and can also determine a preliminary task list state according to the comprehensive task state of the account-closing tasks; for example, assuming that there are 10 account-related tasks in the task list and 8 account-related tasks are completed, that is, when the task completion rate is 80%, the preliminary status of the task list can be considered as the completed status, where the task completion rate is 80% is merely an example, and the task completion rate can be adjusted according to actual specific situations.

After each account clearance task in the account clearance task list is completed or is not completed, each account clearance task may include remarks of respective task progress conditions.

Further, in the embodiment of the present application, a completion result of the ledger task list may be generated according to the completion state of each ledger task, and the completion result may be used to summarize the entire ledger task, show the progress of each organization in the key task, identify whether a task is delayed, show the reason of the delay, and the like, for example, details of each ledger task, the completion time of each ledger task, and the like may be checked, and details of each ledger task that is specifically checked may be integrated, and may be used to predict the ledger risk or provide a management hint for a new ledger task in the future.

For example, the completion result of the ledger task list may include four tables:

(1) and the task condition completion table can contain task progress conditions, and if delay conditions exist in the task progress conditions, the task condition completion table also contains delay reasons.

(2) A task execution list, which is capable of querying all tasks.

(3) And the task flow monitoring table can inquire all time nodes for completing the tasks.

(4) And the task progress monitoring table can integrate and display the results of the generated task condition completion table, the generated task execution detail table and the generated task flow monitoring table.

According to the method and the system, the unified task list is sent to different target organizations, so that the different target organizations can complete execution and operation of related tasks on the unified task template, a manager can manage different organizations through a unified flow system, and compared with the management of different flow systems, the efficiency is improved; meanwhile, task management is executed on a unified task management system, so that a manager can acquire execution details of all tasks, and the task execution transparency is improved; after the management task is completed, the result of task execution can be generated, so that a manager can count the completion conditions of all tasks and control the process risk.

As shown in fig. 3, in some embodiments of the present application, before acquiring a request for a tie-out task of a target tie-out organization in a target time slot under a target business plate, the method further includes the following steps 301 to 302:

301. and defining account clearance task main data used for representing each account clearance task, wherein the account clearance task main data comprises information of an account clearance organization, information of a business plate to which the account clearance task belongs and information of an account clearance task source.

The information of the account clearance organization can be basic information of the organization, and can include main operation information of the organization, such as: organization name, organization address, organization and management information and the like, wherein the management information comprises a management field; the information of the business plate can be the plate differentiation according to the function field, such as building plate, logistics plate, financial plate, etc.; the source information of the account clearance task may be the source information of the account clearance task, which is the account clearance task request sent by each plate.

For example, the specific definition manners of the information of the aforementioned customs clearance organization, the information of the business plate belonging to the business plate, and the information of the source of the customs clearance task may be defined in terms of codes, including defining which section the customs clearance organization is in when defining the customs clearance organization, where the section may be an administrative area, such as a city, a section under the city, or a street, and the like, and when defining the section information, the section codes, the basic information description of the section, and the like may be defined in terms of codes.

In addition, when defining the account closing organization, large area information may be defined, where the large area may be an eastern large area, a western large area, a southern large area, a northern large area, and the like of an administrative area, and may also be a larger-range area, for example, if the large areas may be northwest large area, southwest large area, a middle large area, northeast large area, and a southern china large area according to a territorial area, the specific limitations are not made, and when defining the large area information, a large area code, description of basic information of the large area, and the like may be defined in a coding manner.

Furthermore, when defining the service plate, the plate code and the plate description of the plate can be defined in a coding manner.

Further, when defining a specific account clearance organization, an organization code, a related description of the organization, and the like may also be defined in the above coding manner.

Finally, can judge according to the code to all main data, when the code judges each organizational information, plate information and source information match, can associate the three, wherein, if match according to the mode of code, can have three kinds of matching modes:

(1) for example, direct matching is performed according to the plate code and the code of the account closing task request, and when the plate code and the account closing task request are completely the same, matching is completed.

(2) Or performing partial matching according to the plate code and the code of the account closing task request, for example, when the beginning of the code in two is all fixed characters, such as coding by using English letters, for example, AB, HB, WL and the like are used as the beginning code of the code, and when the beginning codes are matched, the matching is successful.

(3) Or establishing other matching mechanisms to match the block codes with codes of the account-related task requests in other encryption modes, for example, designing corresponding encryption passwords, and completing matching when the two passwords are matched.

When the account clearance task request comprises corresponding organization information, plate information, account clearance task source information and other related information, corresponding permission group codes can be added through the codes.

It should be noted that, in the foregoing embodiment, only a fact manner in a case of this step is described by way of example, and it should be understood that the manner of matching the above-mentioned information is not only a manner of matching only a code, and is not limited herein.

302. And when acquiring a request for creating a ledger task, creating the ledger task according to the ledger task master data.

After the information of the account clearance organization, the target business plate, the source of the account clearance task request, and the like is associated and determined through the related information defined by the account clearance task main data defined in the step 301, a corresponding account clearance task may be created, for example, assuming that the account clearance task request of the logistics plate is obtained according to the above embodiment, the account clearance task information of the logistics plate source may be determined, and meanwhile, the related logistics organization under the logistics plate may be obtained, and the account clearance task related to the logistics organization may be created through the association of the three, instead of the account clearance task of the organization of the financial organization or the building type.

The mode of creating the task can be manually according to which financial data are needed by the logistics organization to create the manual task, and the preset account closing task template can be directly obtained by setting the account closing task of the logistics organization in advance.

As shown in fig. 4, in some embodiments of the present application, before the acquiring, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period, the method further includes the following steps 401 to 403:

401. and defining a clearance task coding strategy.

According to the step 302 of the above embodiment, if a preset account clearance task template is obtained, each preset account clearance task needs to be encoded, where if encoding is performed, an encoding policy needs to be involved. The encoding strategy may be made by a human being or randomly generated by a computer, and may be any one of known encoding strategies, which is not limited herein.

402. And coding preset various types of account clearance tasks according to the account clearance task coding strategy to obtain various types of account clearance task codes.

If a self-defined encoding strategy is adopted, the encoding strategy may be: when a specific account closing task is related, capital english letters can be used as the beginning part of the code, for example, AA begins a task which can be an asset type, GL begins a task which can be a general ledger type, MM begins a task which can be a material type, TR begins a task which can be a fund type, CO begins a task which can be a management ledger type, AR begins a type service which can be receivable, AP begins a type service which can be receivable, and according to the beginning english letters, 4 digits can be additionally added after the english letters, for example, 1234, etc., wherein, the code expandability can be considered, when a task of the same type needs to be additionally added, additional codes can be added, for example: the numerical value of the last four-digit code between two task items may differ by 10, for example, the difference between the task AA1234 and the task AA1224 is 10, when an additional task needs to be inserted, the code AA1225 may be used as the code of the additional task, it should be noted that the coding mode of the first two english letters plus the last four roman numerals is not the only coding mode, and the coding mode of the 6 digits is expanded to 12 at most, for example, AA 0123456789.

Note that, when the encoding is performed in accordance with the above encoding method, the roman numerals may represent different meanings, and when the task is AA0123456789, the meanings represented by the different roman numerals are also different, and for example, the meaning of the unit number 9 may represent: the method comprises the following steps of task numbering, task description, task types, source systems, permission groups, program names, program variables, job names, offset days, plan starting time, plan duration, task priorities, task attributes, applicable plates, key tasks, tax payment correlation and tax payment subject attributes; of course, 8 of the ten digit can also represent any meaning mentioned above, and the roman numerals of other digits can represent any meaning mentioned above, and in practical cases, the adjustment can be made according to specific requirements, and the details are not limited herein.

The tasks which are coded and edited can be put into a user-defined folder, the user-defined file is added into a storage medium with encryption property and is used for managing the tasks which are coded and edited, and when the tasks are required to be called, the tasks can be called through a decryption means, such as inputting a password for decryption, or after decryption by other types of decryption means.

403. And defining a account closing task template corresponding to each service plate through various types of account closing task codes to obtain the account closing task template corresponding to each service plate.

After the service plate to be executed is determined according to the account clearance tasks which are coded and edited, for example, the service plate is a logistics service plate, the logistics service plate is screened out according to the coding, which logistics-related specific account clearance tasks need to be called, and a task template is combined, wherein the task template comprises at least one logistics-related account clearance task.

As shown in fig. 5, in some embodiments of the present application, in creating a clearance task list belonging to the target business plate in the target time period according to the clearance request, the method may further include the following steps 501 to 502:

501. and setting a plurality of account clearance organizations and a plurality of account clearance tasks for each account clearance task, wherein the account clearance organization authority corresponds to each target account clearance organization, and the account clearance organization authority comprises a browsing authority of the account clearance organization and an operation authority of the account clearance organization.

When the account clearance task list is obtained, the authority may be set in combination with each account clearance organization for the task template mentioned in the above embodiment, for example, assuming that the task template under the logistics block is obtained according to the above embodiment, and the number of the logistics organizations under the logistics block is obtained at the same time, the data of the task template and the logistics organizations are combined to perform corresponding authority coding, so that each organization can only browse and operate the account clearance task under its own organization when executing the account clearance task in the account clearance task list.

Illustratively, if there are 3 account-related tasks under the task template of the logistics block, which are A, B, C, respectively, and the logistics under the logistics block are organized as a, B, and C, 9 account-related tasks, namely Aa, Ab, Ac, Ba, Bb, Bc, Ca, Cb, and Cc, can be obtained according to the data of the two tasks, namely, logistics company a can only browse and operate three account-related tasks of Aa, Ba, and Ca, company B can only browse and operate three account-related tasks of Ab, Bb, and Cb, and company C can only browse and operate three account-related tasks of Ac, Bc, and Cc.

502. And acquiring the account clearance task list according to the browsing permission and the operation permission.

After the browsing authority and the operation authority defined by 501 are added to each account clearance task in the account clearance task list, the account clearance task list with the authority added can be obtained.

After the account clearance task list and before the account clearance task list is not published to each account clearance organization, the number of the account clearance tasks in the account clearance task list can be added or deleted.

As shown in fig. 6, in some embodiments of the present application, after obtaining the completion status of each ledger task in the execution of the ledger task list by each ledger organization, the method further includes the following steps 601 to 602:

601. and determining the completion state of each account clearance task in the account clearance task list.

The account-closing task state in this step refers to the current task state of each account-closing task in the task list, and may also be a task completion condition.

For example, the task state may be a completed error-free state, where the completed error-free state is that the task has been executed normally and has been completed; the completed warning state is that the task is completed, but a warning message exists, so that the actual completion is not influenced; the finished error state is that the task is finished and executed, but the returned execution result is an error, and the task needs to be executed again subsequently; the task state mentioned in this embodiment is only one of the manners, and does not limit the defining manner of the other task states.

602. And determining the completion state of the target account clearance organization executing the account clearance task list according to the completion state of each account clearance task.

The status of the account clearance task list is determined by the completion condition of each account clearance task in the account clearance task list, and if more than 90% of the tasks in the account clearance task list are completely completed, the account clearance task list can be determined to be completed, and the threshold value of 90% can be adjusted, for example, to 100%, that is, when all the account clearance tasks in the account clearance task list are completed, the account clearance task list is in a completed status.

If the determination of the account clearance task list is needed, the determination can be also performed through other manners, such as:

if at least one account clearance task in the account clearance task list is finished, determining that the account clearance task list is in an activated state; for example, the activation state may be represented by the letter a;

if all tasks in the account clearance task list are finished, determining that the account clearance task list is in a finished state; for example, the activation state may be represented by the letter F;

if the current task in the account clearance task list is in a pause state, determining that the account clearance task list is in the pause state; for example, the activation state may be represented by the letter L;

if the account clearance task list is not issued to the target account clearance organization after the account clearance task list is established, determining that the account clearance task list is in an unpublished state; for example, the activation state may be represented by the letter N;

if the clearance task list is already published to the target clearance organization after the clearance task list is established, determining that the clearance task list is in a published state; for example, the activation state may be indicated by the letter X.

After the account clearance task list is published, each account clearance organization starts to execute each account clearance task in the account clearance task list, and when each account clearance organization executes a task, the task state changes, for example, when a unit time including a working day passes, the task is completed by the account clearance organization, the task state changes from an incomplete state to a complete state, and at this time, the task state needs to be updated.

Wherein, the checking the status of the current account clearance task in the account clearance task list according to a preset period includes:

Determining the following types of the current account clearance task in the condition of checking the currently executed account clearance task in the account clearance task list through a preset period:

1) if the current account clearance task is being processed, determining the task state of the current account clearance task as the processing state;

2) if the current account clearance task does not start to be processed, determining that the task state of the current account clearance task is an unprocessed state;

3) if the current account clearance task is finished and has no error, determining the task state of the current account clearance task as a finished error-free state;

4) if the current account clearance task is finished but a warning message exists, and the actual completion is not influenced, determining that the task state of the current account clearance task is a finished warning state;

5) if the current account clearance task is finished, but the returned execution result is an error, and the account clearance task needs to be executed again subsequently, determining that the task state of the current account clearance task is a finished error state;

6) and if the current account clearance task is finished and normally finished, determining that the task state of the current account clearance task is the checked state.

The task state of the account clearance task can be determined manually according to the task state of the account clearance task, or can be determined by other computer software or systems.

For example, after the task status can be determined, periodic scanning of tasks and execution of tasks can be performed by an SAP (system applications and products in data processing) system, where task completion can be manually confirmed and task status can be modified, and in addition, the system also automatically distributes any SAP system for automatic execution according to task dependency relationship or timing configuration, and the system automatically updates task status after execution is completed, and supposing that, after execution of a task of an operation type is completed, the task status with a transaction code, for example, a check code of ZFI525, can be synchronized to an SAP accounting system through the transaction code.

The SAP system proposed in this implementation is: the SAP system, also known as an enterprise management solution, functions as: the management system is customized and established for the enterprise by means of a software program, supervision, analysis and management are carried out on all operational activities and links of the enterprise, such as human resources, logistics transportation, sales service, transaction payment, product specification and quality, production activities, raw material purchasing, goods storage, inventory management and the like, a digitalized resource management system is formed, guidance and basis are provided for production, decision making and organization operation of the enterprise, the financial management quality of the enterprise is improved, and the reasonable allocation of capital of the enterprise is facilitated.

It should be noted that the SAP system is only one way of the embodiment of the present application, and is not limited to other ways.

In some embodiments of the present application, after obtaining a completion status of each ledger organization executing each ledger task in the ledger task list, the method may further include:

and if the task state needs to be changed, changing the task state.

When the closed account task list is closed and the tasks in the account-related task list need to be updated, for example, after the closed account task list is closed, the tasks in the account-related task list are executed incorrectly in the execution process, so that the generated result is not in line with the expectation, and the tasks need to be re-executed, the tasks can be changed by establishing a policy for changing the task state.

In some embodiments of the present application, after obtaining the completion status of each ledger organization executing each ledger task in the ledger task list, the method further includes the following policy:

(1) if the task state of the pre-account clearance task is the completed no-error state, the completed warning state or the checked state, the post-account clearance task can change the task state when a task state change request is acquired.

The pre-task in the embodiment of the application is a necessary condition of the post-task, that is, the post-task can be executed only after the pre-task is completed. That is, when the current state of the post task is not completed when the current task is completed, the state can be changed to the completed task state after the post task is completed.

(2) And if the task state of the pre-account clearance task is the in-process state and the completed error state, and when a task state change request is acquired, the post-account clearance task cannot change the task state.

The front task and the rear task in the strategy are the same as the front task, and when the front task is in an incomplete state, the rear task cannot be started, so that even if the rear task is already executed by a corresponding account-closing task organization, the task state of the rear task cannot be changed from incomplete to incomplete.

(3) And if the task state of the pre-customs clearance task is changed when the post-customs clearance task is finished and the task state of the pre-customs clearance task is changed, and the task state of the post-customs clearance task is automatically changed into the finished error state when a task state change request is acquired.

When the pre-task and the post-task are both completed, if the pre-task needs to change the task state for a special reason, for example, the completed state is changed to an uncompleted state, the situation at this time is similar to the policy at point (2) in the embodiment of the present application, that is, the pre-task belongs to the uncompleted state, and the post-task should be in the uncompleted state, but the completed result of the post-task is uploaded at this time, so the state of the post-task at this time is changed to the completed error state.

(4) And if the task state of the front account clearance task is a finished error-free state and a checked state, prompting whether the rear account clearance task starts immediately, starting the rear account clearance task when the selected information is acquired, and finishing executing the rear account clearance task when the selected information is acquired.

When the task state is changed, a change reason can be input, so that subsequent query is facilitated; and when the task state is changed to be completed, no error exists or the task is checked, prompting whether the task is planned to be started immediately or not after confirmation, if so, sending the task to the SAP system, and otherwise, ending.

When the SAP system is used for executing the account clearance task list, actual execution is not influenced when the duration of an account clearance task plan is exceeded, and if the duration of the account clearance task plan is exceeded, tasks can still be executed in the platform. If the account closing task list has the operation tasks, the operation is automatically carried out, but the operation is carried out only once, and the functions of detecting newly added data and the like cannot be realized; for example, GR/IR re-sorting SSP, after the system is executed, the state shows green light, new data is transmitted from the front end, and the task state in the system is not changed.

The GR/IR is Goods Recipt/Invitation Recipt, and in SAP system, GR/IR is a transitional subject used for recording the in-transit materials and temporary payment estimation, and the aim is to obtain financial statements.

The SAP system divides the checking and account-entering of the goods-receiving and the invoice into two departments, the goods-receiving action is GR, the goods-receiving action is the inventory account-entering action, the goods-borrowing and account-transferring subjects are carried out by the warehouse, when the invoice is received, the finance department carries out the invoice checking and account-entering action, the goods-borrowing and account-transferring subjects are borrowed and account-payable, and thus the transition of the goods-borrowing party is cleared.

The SSP (supply Side platform) is a supplier platform that enables publishers to also intervene in ad transactions to make their inventory ads available. Through this platform, vendors expect that their inventory ads can be offered the highest effective exposure cost per thousand, rather than having to be sold at a low price.

As shown in fig. 7, in some embodiments of the present application, after acquiring the completion status of each ledger task executed by each ledger organization in the ledger task list, the method may further include the following steps 701 to 704:

701. and when the completion state of each actual account clearance task in the account clearance task list is consistent with the current completion state of each account clearance task, finishing executing the account clearance task list.

702. And when the current completion state of at least one account clearance task is inconsistent with the actual account clearance completion state, prompting whether the account clearance task list is completed or not.

And when the user selects the corresponding account closing task list and clicks to close the task list, the task list is changed into the completed task list, and if the task which is completed at the moment still exists but is not sent to the SAP system, the user is prompted that the task list has the incomplete items.

703. And if the information selected as yes by the user is acquired, finishing executing the account clearance task list.

And clicking the closed account closing task list to open again, executing the account closing task again after the closed account closing task list is opened, clicking the closed account closing task list again after the adjustment is completed, completing the closed loop of the account closing flow, and stopping scanning the account closing task list by the scanning program after the account closing task list is closed.

704. And if the information selected by the user is not acquired, continuing to execute the account clearance task list.

As shown in fig. 8, in some embodiments of the present application, there is further provided a cross-organization customs clearance task management method, including the following steps 801 to 804:

801. and acquiring a plurality of clearance requests of the target clearance organization in a second target time period.

In this step, a plurality of clearance requests may be obtained at the same time, and the rest is the same as that in step 201, which is not described herein again.

802. And creating each account closing task list belonging to each business plate in the second target time period according to the plurality of account closing requests, wherein each account closing task list comprises a plurality of account closing tasks organized by a plurality of target account closing.

In this step, a plurality of account clearance tasks may be executed simultaneously, a plurality of account clearance task lists may be created simultaneously according to different target boards and different target organizations, and the account clearance tasks may be executed simultaneously, and other aspects are the same as those in step 202, and thus are not described herein again.

803. And issuing the each account clearance task list to the plurality of target account clearance organizations, so that the plurality of target account clearance organizations execute the account clearance tasks associated with the target account clearance tasks in the associated account clearance task lists.

In this step, a plurality of target account clearance organizations can execute the tasks related to the target account clearance in different account clearance task lists at the same time, and the rest is the same as that in the step 203, so that the detailed description is omitted here.

804. And acquiring the completion state of each account closing task in the account closing task list which is associated with each target account closing organization and executed by each target account closing organization.

In this step, the completion status of each of the plurality of the account clearance tasks in the account clearance task list can be obtained, and the rest is the same as that in step 204, which is not described herein again.

In order to better implement the cross-organization task management method in the embodiment of the present application, in addition to cross-organization task management, an embodiment of the present application further provides a cross-organization task management device, as shown in fig. 9, the cross-organization task management device 900 includes:

a first obtaining module 901, configured to obtain a clearance request of a target clearance organization in a target time period under a target service plate;

a creating module 902, configured to create, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period, where the account clearance task list includes multiple account clearance tasks organized by multiple account clearances;

an issuing module 903, configured to issue the ledger task list to the multiple ledger organizations, so that each ledger organization executes a ledger task associated with the ledger task list;

a second obtaining module 904, configured to obtain a completion state of each account clearance task executed by each account clearance organization in the account clearance task list.

According to the method, after the first acquiring module 901 and the creating module 902 acquire the account clearance request, unified task lists are sent to different target organizations through the issuing module 903, so that the different target organizations can complete execution and operation of related tasks on unified task templates, and the completion state of each account clearance task is acquired through the second acquiring module 904, so that a manager can manage the different organizations through a unified flow system, and the efficiency is improved compared with the management of different flow systems; meanwhile, task management is executed on a unified task management system, so that a manager can acquire execution details of all tasks, and the task execution transparency is improved; after the management task is completed, the result of task execution can be generated, so that a manager can count the completion conditions of all tasks and control the process risk.

the first obtaining module is specifically configured to:

and defining a customs account task template corresponding to the service plate through the code of each customs account task to obtain a corresponding customs account task template.

the creation module is specifically configured to:

the second obtaining module is specifically further configured to:

An embodiment of the present application further provides a cross-organization task management device, which integrates any one of the cross-organization task management apparatuses provided in the embodiment of the present application, where the cross-organization task management device includes:

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 steps in cross-organizational task management described in any embodiment.

An embodiment of the present application further provides a cross-organization task management device, which integrates any one of the cross-organization task management methods provided in the embodiment of the present application, and as shown in fig. 10, it shows a schematic structural diagram of the cross-organization task management device according to the embodiment of the present application, specifically:

the cross-organizational task management device may include components such as a processor 1001 of one or more processing cores, memory 1002 of one or more computer-readable storage media, a power source 1003, and an input unit 1004. Those skilled in the art will appreciate that the cross-organizational task management device structure shown in FIG. 10 does not constitute a limitation of the cross-organizational task management device, and may include more or fewer components than shown, or some components combined, or a different arrangement of components. Wherein:

the processor 1001 is a control center of the cross-organization task management device, connects various parts of the entire cross-organization task management device by using various interfaces and lines, and executes various functions and processes data of the cross-organization task management device by running or executing software programs and/or modules stored in the memory 1002 and calling data stored in the memory 1002, thereby integrally monitoring the cross-organization task management device. Optionally, processor 1001 may include one or more processing cores; the Processor 1001 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and preferably the processor 1001 may integrate an application processor, which handles primarily the operating system, user interfaces, application programs, etc., and a modem processor, which handles primarily wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1001.

The memory 1002 may be used to store software programs and modules, and the processor 1001 executes various functional applications and data processing by operating the software programs and modules stored in the memory 1002. The memory 1002 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created from use of the cross-organization task management device, and the like. Further, the memory 1002 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic 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 access to the memory 1002.

The cross-organization task management device further comprises a power source 1003 for supplying power to each component, and preferably, the power source 1003 can be logically connected with the processor 1001 through a power management system, so that functions of charging, discharging, power consumption management and the like can be managed through the power management system. The power source 1003 may also include any component including one or more of a dc or ac power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.

The cross-organizational task management device may also include an input unit 1004, where the input unit 1004 may be used to receive entered numeric or character information and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

Although not shown, the cross-organization task management device may further include a display unit and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 1001 in the cross-organization task management device loads the executable file corresponding to the process of one or more application programs into the memory 1002 according to the following instructions, and the processor 1001 runs the application programs stored in the memory 1002, so as to implement various functions, for example:

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

To this end, an embodiment of the present application provides a computer-readable storage medium, which may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like. The computer program is loaded by a processor to execute the steps of any one of the cross-organization task management methods provided by the embodiments of the present application. For example, the computer program may be loaded by a processor to perform the steps of:

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed descriptions of other embodiments, and are not described herein again.

In a specific implementation, each unit or structure may be implemented as an independent entity, or may be combined arbitrarily to be implemented as one or several entities, and the specific implementation of each unit or structure may refer to the foregoing method embodiment, which is not described herein again.

The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.

The cross-organization task management method and device provided by the embodiment of the present application are introduced in detail, a specific example is applied in the description to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A cross-organization account closing task management method is characterized by comprising the following steps:

2. The cross-organization accounting task management method according to claim 1, before the acquiring accounting task request of the target accounting organization in the target time period under the target business plate, the method further comprises:

and when acquiring a request for creating a customs account task, creating the customs account task according to the main data of the customs account task.

3. The cross-organization account clearance task management method according to claim 1, wherein before the acquiring, according to the account clearance request, an account clearance task list belonging to the target business plate in the target time period, the method further comprises:

defining a customs account task coding strategy;

4. The cross-organization account clearance task management method according to claim 1, wherein the creating an account clearance task list belonging to the target business plate in the target time period according to the account clearance request includes:

and creating the account clearance task list according to the browsing permission and the operation permission.

5. The cross-organization ledger task management method according to claim 1, wherein after the acquiring of the completion status of each ledger task in the execution of the ledger task list by each ledger organization, the method further comprises:

6. The cross-organization ledger task management method according to claim 5, wherein the determining the completion status of the target ledger organization executing the ledger task list according to the completion status of the ledger tasks comprises:

if at least one account clearance task in the account clearance task list is finished, determining that the account clearance task list is in an activated state;

7. The cross-organization ledger task management method according to claim 5, wherein after determining the completion status of the target ledger organization executing the ledger task list according to the completion status of the respective ledger tasks, the method further comprises:

8. The cross-organization account clearance task management method according to claim 7, wherein the checking the status of the currently executed account clearance task in the account clearance task list according to a preset period comprises:

9. The cross-organization account clearance task management method according to claim 8, wherein the acquiring the task state of each account clearance task in the account clearance task list according to a preset period comprises:

10. The cross-organization ledger task management method according to claim 9, wherein after acquiring the completion status of each ledger organization executing each ledger task in the ledger task list, the method further comprises:

11. The cross-organization ledger task management method according to claim 1, wherein after acquiring the completion status of each ledger organization executing each ledger task in the ledger task list, the method further comprises:

12. A cross-organization account closing task management method is characterized by comprising the following steps:

acquiring a plurality of clearance requests of a target clearance organization in a second target time period;

and acquiring the completion state of each account clearance task executed by the plurality of target account clearance organizations in the account clearance task list associated with the target account clearance organizations.

13. A cross-organizational task management apparatus, comprising:

the issuing module is used for issuing the account clearance task list to the plurality of account clearance organizations so that each account clearance organization executes the account clearance task associated with the account clearance task list;

14. A cross-organization task management device, the cross-organization task management device comprising:

one or more processors;

a memory; and

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 cross-organizational task management method of any of claims 1 to 12.

15. A computer readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the steps of the cross-organizational ledger task management method of any one of claims 1 to 12.