Automatic expenditure management method and system

[0027] Embodiment 1. An automatic payment management method. Combine below Figure 1-Figure 4 The method provided in this embodiment will be described.

[0028] see figure 1 , The method provided in this embodiment includes: S1. Abstract each step of the entire billing process as an event, and configure N conditions that each event execution needs to depend on, where N is a positive integer greater than or equal to 1.

[0029] Specifically, the entire billing process may include many steps, for example, M steps, where M is a positive integer greater than or equal to 1. For the convenience of description, this embodiment abstracts each step in the entire billing process as an event. As before, the entire billing process includes M events. Configure the N conditions that the execution needs to depend on for each event, that is, each event must meet these N conditions before it can be executed. In addition, the latest start execution time and latest end execution time are set fo

[0039] Embodiment 2, an automatic account payment management system. Combine below Figure 5 The system provided by this embodiment is described.

[0040] see Figure 5 The system provided in this embodiment includes a configuration unit 51 , a condition judgment unit 52 , an execution unit 53 , an execution result acquisition unit 54 , a status update unit 55 , a verification unit 56 and an abnormality alarm unit 57 .

[0041] The configuration unit 51 is mainly used to abstract each step of the entire billing process into an event, and configure the event identifier of each event and N conditions on which the execution of each event depends, where N is a positive integer.

[0042] The condition judging unit 52 is mainly used for judging whether the N conditions on which the execution of each event depends are established according to the first predetermined time interval.

[0043] Execution unit 53 is mainly used to execute the event if the N conditions that the event execut