Abstract: Systems and methods are disclosed for financial planning based on actual cash positions for financial accounts associated with an entity and planned cash out and cash in amounts for the entity. In an embodiment, a system comprises a processor configured to render an interactive graphical user interface (“GUI”) on a display device. The GUI has a plurality of selectable, actionable user interface elements such as tabs. In an embodiment, the GUI comprises a first tab selectable to display actual and planned net amount information of a cash position and actual and planned net amount graphs, the net amount information being cash out amounts subtracted from cash in amounts. The GUI comprises a second tab operable to display actual and planned cash in amount information and actual and cash in amount graphs. In an embodiment, the GUI comprises a third tab operable to display actual and planned cash out amount information and actual and planned cash out amount graphs.

Abstract: Systems and methods are disclosed for managing cash out transactions for an entity's accounts. In an embodiment, a system comprises a processor configured to render an interactive graphical user interface (GUI) for a cash out center on a display device. The GUI includes plurality of selectable, actionable user interface (UI) elements. The cash out center displays past and committed, unconfirmed Cash Out transactions, which can be edited, deleted, and committed (or re-committed) by selecting UI elements. A UI element is selectable to add new payees and new Cash Out transactions. In embodiments, methods employ the Cash Out center to add, edit, schedule and delete Cash Out transactions such as outgoing transfers, expenses, payments, bills, and payables.

Abstract: Systems and methods are disclosed for managing cash flow, including incoming and outgoing transactions, and mitigating unconfirmed cash shortfalls for an entity's accounts. In an embodiment, a system comprises a processor configured to render an interactive graphical user interface (“GUI”) for the cash flow timeline on a display device. The cash flow timeline displays past and unconfirmed Cash In and Cash Out transactions and any cash shortfalls, which can be mitigated by selecting automatically displayed options. The GUI has a plurality of selectable, actionable user interface (“UI”) elements. In an embodiment, the GUI comprises a UI element selectable to display bar graphs for selected time periods of the cash flow timeline. The GUI also comprises Cash In and Cash Out centers. In embodiments, methods employ the Cash In/Out centers to add, edit, schedule and delete Cash In and Cash Out transactions such as transfers, expenses, bills, receivables, and payables.

Abstract: Systems and methods are disclosed for managing cash in transactions for an entity's accounts. In an embodiment, a system comprises a processor configured to render an interactive graphical user interface (GUI) for a cash in center on a display device. The GUI includes plurality of selectable, actionable user interface (UI) elements. The cash in center displays past, unconfirmed and ‘confirmed’ Cash in transactions, which can be edited, deleted, and scheduled (or re-scheduled) by selecting UI elements. A UI element is selectable to add new customers and new Cash in transactions. In embodiments, methods employ the Cash in center to add, edit, project, and delete Cash in transactions such as incoming transfers, credits, customer payments, and receivables. The methods and system also enable entities to place Cash In transaction in a confirmed status to indicate that an incoming customer payment, credit, or transfer is being processed.

Abstract: A system for disrupting malware includes a transform function and its inverse transform function which, when applied serially to an original bit pattern will return the original bit pattern, but when applied in solo will result in a bit pattern which is different than the original bit pattern, a preprocessor configured to apply the transform function in order to transform each benign program received from the computer-readable medium from an architecturally standardized form into a locally-specific form prior to storage of the program code in the program memory; a postprocessor configured to apply the inverse transform function in order to inversely transform all programs prior to their execution, such that previously transformed benign programs are converted back to the architecturally standardized form and malicious programs are rendered dysfunctional for their intended purpose.

Abstract: Systems and methods for disrupting the operational capabilities and the distribution capabilities of computer viruses are provided. According to one embodiment, an execution environment is created that makes a computer system appear unique to incoming viruses. Responsive to installation of a valid program, the program is registered for execution by transforming it from an executable form into a locally unique form based on a diversity mechanism. Responsive to detecting an attempted execution of a program and prior to execution of the program, it is transformed by causing a protected pre-execution process of the computer system, which implements the diversity mechanism in the form of an inverse transform, to be applied. If the program was previously validly registered, then the transformation based on the diversity mechanism results in an executable program that will execute properly on the computer system; otherwise the transformation results in an executable program that will fail to correctly execute.

Abstract: A method for parsing and executing a software program includes receiving a portion of a software program in an original linguistic form, wherein the portion of the software program includes a nonlinear program element having a body, and, while retaining the original linguistic form, directly executing the nonlinear program element by manipulating a parse state and an input stream of tokens representing the body of the nonlinear program element, wherein directly executing comprises executing tokens until the dynamic end of the nonlinear program element is reached. A system includes a tokenizer operable to tokenize the software program and a parser operable to directly execute a nonlinear program element in the software program by manipulating a parse state and an input stream of tokens representing the body of the nonlinear program element, while preserving the original linguistic form of the software program.