BUDGET APPROVAL WORKFLOW CONFIGURATION SYSTEM AND METHOD
A budget approval workflow configuration system (BAWCS) includes a graphical user interface (GUI) to be output by a user interface (UI), the GUI including a first user input field configured to receive a first user input identifying a budget administrator; a second user input field configured to receive a second user input identifying a first reviewer to perform first reviewer responsibilities; a third user input field configured to receive a third user input identifying a workflow action based on a first reviewer approval or rejection of a budget; a fourth user input field configured to receive a fourth user input identifying a workflow location for the budget based on the first reviewer approval or rejection of the budget; and a fifth user input field configured to receive a fifth user input identifying email addresses to provide email notification for a corresponding operation within a budget approval process.
1 . A budget approval workflow configuration system (BAWCS), comprising:
a memory having non-transitory instructions stored therein; and
processing circuitry coupled to the memory, and being configured to execute the non-transitory instructions, thereby causing the processing circuitry to:
cause a graphical user interface (GUI) to be output by a user interface (UI), the GUI comprising:
a first user input field configured to receive a first user input identifying a budget administrator to log in to the BAWCS;
in response to a successful log in to the BAWCS, obtain master data from the memory, the master data being associated with the budget administrator; and
update the GUI output by the UI, the updated GUI comprising:
a presentation of a budget associated with the budget administrator;
a second user input field configured to receive a second user input identifying a first reviewer to perform first reviewer responsibilities;
a third user input field configured to receive a third user input identifying a workflow action based on a first reviewer approval or rejection of a budget;
a fourth user input field configured to receive a fourth user input identifying a workflow location for the budget based on the first reviewer approval or rejection of the budget; and
a fifth user input field configured to receive a fifth user input identifying email addresses to provide email notification for a corresponding operation within a budget approval process.
2 . The BAWCS of claim 1 , wherein the GUI further comprising:
a sixth user input field configured to receive a sixth user input identifying a sequential reviewer after the first reviewer, wherein the budget administrator inputs up to N reviewers, where N is a non-zero positive integer, that sequentially receive and review the budget after each sequential budget approval beginning with the first reviewer approval.
3 . The BAWCS of claim 2 , wherein the GUI further comprising:
a seventh user input field configured to receive a seventh user input identifying an effective start date for assigned reviewer responsibilities.
4 . The BAWCS of claim 3 , wherein the non-transitory instructions further cause the processing circuitry to:
activate an approval workflow based on the effective start date.
5 . The BAWCS of claim 4 , wherein the non-transitory instructions further cause the processing circuitry to:
retrieve active approval flow for each budget type; and
obtain execution operations in the approval workflow to the budget.
6 . The BAWCS of claim 5 , wherein the non-transitory instructions further cause the processing circuitry to:
execute a first execution operation based on a first user submitting the budget.
7 . The BAWCS of claim 6 , wherein the non-transitory instructions further cause the processing circuitry to:
in response to execution of the first execution operation, transfer the budget to the first reviewer; and
send a budget application email to the first reviewer and additional emails designated by the budget administrator.
8 . The BAWCS of claim 7 , wherein the non-transitory instructions further cause the processing circuitry to:
receive the first reviewer approval or rejection.
9 . The BAWCS of claim 8 , wherein the non-transitory instructions further cause the processing circuitry to:
in response to the first reviewer approval, change a status of the budget to approved in the first execution operation; and
execute a next sequential execution operation.
10 . The BAWCS of claim 8 , wherein the non-transitory instructions further cause the processing circuitry to:
in response to the first reviewer rejection, change a status of the budget to rejected in the first execution operation; and
send a rejected budget application email along with comments by the first reviewer to the first user submitting the budget.
11 . The BAWCS of claim 10 , wherein the non-transitory instructions further cause the processing circuitry to:
record each action; and
update the GUI output by the UI, the GUI comprising:
an updated budget workflow.
12 . The BAWCS of claim 11 , wherein the non-transitory instructions further cause the processing circuitry to:
determine whether a final execution operation has been executed and approval made by a final reviewer; and
send an email of a completed budget application to the first user submitting the budget and each reviewer of the budget.
13 . A method executed by processing circuitry, the method comprising:
causing a graphical user interface (GUI) to be output by a user interface (UI), the GUI comprising:
a first user input field configured to receive a first user input identifying a budget administrator to log in to a budget approval workflow configuration system (BAWCS);
in response to a successful log in to the BAWCS, obtaining master data associated with the budget administrator; and
updating the GUI output by the UI, the GUI further comprising:
a presentation of each budget associated with the budget administrator;
a second user input field configured to receive a second user input identifying a first reviewer to perform first reviewer responsibilities;
a third user input field configured to receive a third user input identifying a workflow action based on a first reviewer approval or rejection of a budget;
a fourth user input field configured to receive a fourth user input identifying a workflow location for the budget based on the first reviewer approval or rejection of the budget; and
a fifth user input field configured to receive a fifth user input identifying email addresses to provide email notification for each operation within a budget approval process.
14 . The method of claim 13 , wherein the GUI output by the UI further comprising:
a sixth user input field configured to receive a sixth user input identifying a sequential reviewer after the first reviewer, wherein the budget administrator inputs up to N reviewers, where N is a non-zero positive integer, that sequentially receive and review the budget after each sequential budget approval beginning with the first reviewer approval.
15 . The method of claim 13 , wherein the GUI output by the UI further comprising:
a seventh user input field configured to receive a seventh user input identifying an effective start date for assigned reviewer responsibilities.
16 . A non-transitory computer readable medium including instructions executable by a controller to perform operations comprising:
causing a graphical user interface (GUI) to be output by a user interface (UI), the GUI comprising:
a first user input field configured to receive a first user input identifying a budget administrator to log in to a budget approval workflow configuration system (BAWCS);
in response to a successful log in to the BAWCS, obtaining master data associated with the budget administrator; and
updating the GUI output by the UI, the GUI further comprising:
a presentation of each budget associated with the budget administrator;
a second user input field configured to receive a second user input identifying a first reviewer to perform first reviewer responsibilities;
a third user input field configured to receive a third user input identifying a workflow action based on a first reviewer approval or rejection of a budget;
a fourth user input field configured to receive a fourth user input identifying a workflow location for the budget based on the first reviewer approval or rejection of the budget; and
a fifth user input field configured to receive a fifth user input identifying email addresses to provide email notification for each operation within a budget approval process.
17 . The non-transitory computer readable medium of claim 16 , wherein the GUI output by the UI further comprising:
a sixth user input field configured to receive a sixth user input identifying a sequential reviewer after the first reviewer, wherein the budget administrator inputs up to N reviewers, where N is a non-zero positive integer, that sequentially receive and review the budget after each sequential budget approval beginning with the first reviewer approval.
18 . The non-transitory computer readable medium of claim 17 , wherein the GUI output by the UI further comprising:
a seventh user input field configured to receive a seventh user input identifying an effective start date for assigned reviewer responsibilities.
19 . The non-transitory computer readable medium of claim 18 , wherein the instructions executable by a controller further performs operations comprising:
activating an approval workflow based on the effective start date.
20 . The non-transitory computer readable medium of claim 19 , wherein instructions executable by a controller further performs operations comprising:
retrieving active approval flow for each budget type; and
obtaining execution operations in the approval workflow to the budget.