Techniques for generating transaction forecasts

1 . A computer-implemented method for generating a graphical user interface, the computer-implemented method comprising:

accessing, by at least one processing device, a forecast transaction template that defines a triggering event and at least one additional transaction event;

detecting, by the at least one processing device, the triggering event occurring with respect to a client account, wherein the triggering event comprises an overdraft fee associated with the client account;

in response to detecting the triggering event:

determining a set of transaction events by:

predicting, by the at least one processing device, a set of expected charges at the client account; and

identifying, by the at least one processing device, the at least one additional transaction event relevant to the transaction forecast template, the at least one additional transaction event comprising a pending transaction transitioning to a posted transaction; and

constructing, by the at least one processing device, a timeline of the set of transaction events and the triggering event;

generating the graphical user interface, wherein the graphical user interface comprises:

a playback bar comprising a toggle, a first event indicator representing the pending transaction, and a second event indicator representing the posted transaction; and

a forecast visualizer, wherein the playback bar and the forecast visualizer are overlaid on an account page associated with the client account, wherein the account page is within a webpage or a mobile application, wherein the forecast visualizer comprises an animation of the set of transaction events based on the timeline, wherein the animation comprises a pending section and a posted section, and wherein the toggle is selectable by a user to control the animation; and

outputting, by the at least one processing device, the graphical user interface at a client device, wherein the outputting the graphical user interface comprises:

outputting the animation in a first configuration that shows the set of transaction events prior to the triggering event, wherein the pending transaction is in the pending section in the first configuration; and

automatically rearranging the set of transaction events to output the animation in a second configuration that shows the set of transaction events after the triggering event, wherein the automatic rearranging of the set of transaction events comprises moving the pending transaction from the pending section to the posted section to show the transition of the pending transaction to the posted transaction.

2 . The computer-implemented method of claim 1 , wherein predicting the set of expected charges comprises applying a machine-learning model to a set of historical charges at the client account to generate the set of expected charges.

3 . The computer-implemented method of claim 1 , further comprising:

determining a modified transaction event of the at least one additional transaction event, wherein the modified transaction event was modified from an original transaction event; and

adding a transition from the original transaction event to the modified transaction event to the timeline.

4 . The computer-implemented method of claim 3 , wherein the transition from the original transaction event to the modified transaction event comprises the pending transaction transitioning to the posted transaction.

5 . The computer-implemented method of claim 1 , further comprising:

identifying additional processing events and contextual notifications, wherein the timeline comprises the additional processing events and the contextual notifications.

6 . The computer-implemented method of claim 5 , wherein the additional processing events comprise a predicted end of day posted account balance, and wherein a second triggering event defined by the transaction forecast template comprises a negative value of the predicted end of day posted account balance.

7 . A system, comprising:

a first computing device; and

a second computing device configured to communicate with the first computing device;

the first computing device configured to perform operations including:

accessing a forecast transaction template that defines a triggering event and at least one additional transaction event;

detecting the triggering event occurring with respect to a client account, wherein the triggering event comprises an overdraft fee associated with the client account;

in response to detecting the triggering event:

determining a set of transaction events by:

predicting a set of expected charges at the client account; and

identifying the at least one additional transaction event relevant to a transaction forecast template, the at least one additional transaction event comprising a pending transaction transitioning to a posted transaction;

constructing a timeline of the set of transaction events and the triggering event;

generating a graphical user interface, wherein the graphical user interface comprises:

a playback bar comprising a toggle, a first event indicator representing the pending transaction, and a second event indicator representing the posted transaction; and

a forecast visualizer, wherein the playback bar and the forecast visualizer are overlaid on an account page associated with the client account, wherein the account page is within a webpage or a mobile application, wherein the forecast visualizer comprises an animation of the set of transaction events based on the timeline, wherein the animation comprises a pending section and a posted section, and wherein the toggle is selectable by a user to control the animation; and

outputting the graphical user interface at a client device, wherein the outputting the graphical user interface comprises:

outputting the animation in a first configuration that shows the set of transaction events prior to the triggering event, wherein the pending transaction is in the pending section in the first configuration; and

automatically rearranging the set of transaction events to output the animation in a second configuration that shows the set of transaction events after the triggering event, wherein the automatic rearranging of the set of transaction events comprises moving the pending transaction from the pending section to the posted section to show the transition of the pending transaction to the posted transaction.

8 . The system of claim 7 , wherein the second computing device is configured to perform operations comprising:

rendering the graphical user interface at the second computing device.

9 . The system of claim 7 , wherein the first computing device is further configured to perform operations comprising:

determining a modified transaction event of the at least one additional transaction event, wherein the modified transaction event was modified from an original transaction event; and

adding a transition from the original transaction event to the modified transaction event to the timeline.

10 . The system of claim 9 , wherein the transition from the original transaction event to the modified transaction event comprises the pending transaction transitioning to the posted transaction.

11 . The system of claim 7 , wherein the first computing device is further configured to perform operations comprising:

identifying additional processing events and contextual notifications, wherein the timeline comprises the additional processing events and the contextual notifications.

12 . The system of claim 11 , wherein the additional processing events comprise a predicted end of day posted account balance, and wherein a second triggering event defined by the transaction forecast template comprises a negative value of the predicted end of day posted account balance.

13 . A non-transitory computer readable medium having stored therein instructions that are executable by a processing device for causing the processing device to perform operations including:

accessing a forecast transaction template that defines a triggering event and at least one additional transaction event;

detecting the triggering event occurring with respect to a client account, wherein the triggering event comprises an overdraft fee associated with the client account;

in response to detecting the triggering event:

determining a set of transaction events by:

predicting a set of expected charges at the client account; and

identifying the at least one additional transaction event relevant to the transaction forecast template, the at least one additional transaction event comprising a pending transaction transitioning to a posted transaction;

constructing a timeline of the set of transaction events and the triggering event;

generating a graphical user interface, wherein the graphical user interface comprises:

a playback bar comprising a toggle, a first event indicator representing the pending transaction, and a second event indicator representing the posted transaction; and

a forecast visualizer, wherein the playback bar and the forecast visualizer are overlaid on an account page associated with the client account, wherein the account page is within a webpage or a mobile application, wherein the forecast visualizer comprises an animation of the set of transaction events based on the timeline, wherein the animation comprises a pending section and a posted section, and wherein the toggle is selectable by a user to control the animation; and

outputting the graphical user interface at a client device, wherein the outputting the graphical user interface comprises:

outputting the animation in a first configuration that shows the set of transaction events prior to the triggering event, wherein the pending transaction is in the pending section in the first configuration; and

automatically rearranging the set of transaction events to output the animation in a second configuration that shows the set of transaction events after the triggering event, wherein the automatic rearranging of the set of transaction events comprises moving the pending transaction from the pending section to the posted section to show the transition of the pending transaction to the posted transaction.

14 . The non-transitory computer readable medium as defined in claim 13 , further comprising instructions for performing operations including:

determining a modified transaction event of the at least one additional transaction event, wherein the modified transaction event was modified from an original transaction event; and

adding a transition from the original transaction event to the modified transaction event to the timeline.

15 . The non-transitory computer readable medium as defined in claim 14 , wherein the transition from the original transaction event to the modified transaction event comprises the pending transaction transitioning to the posseted transaction.

16 . The non-transitory computer readable medium as defined in claim 15 , wherein the pending transaction transitioning to the posted transaction comprises a change in a value of the original transaction event.

17 . The non-transitory computer readable medium as defined in claim 13 , wherein predicting the set of expected charges comprises applying a machine-learning model to a set of historical charges at the client account to generated the set of expected charges.