Database system for triggering event notifications based on updates to database records
US-2024419652-A1 · Dec 19, 2024 · US
US9965808B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9965808-B1 |
| Application number | US-201314098698-A |
| Country | US |
| Kind code | B1 |
| Filing date | Dec 6, 2013 |
| Priority date | Dec 6, 2012 |
| Publication date | May 8, 2018 |
| Grant date | May 8, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
We claim: 1. A system for managing incoming cash flow for one or more financial accounts based on cash in transactions, the system comprising: a display; a processor; and a non-transitory computer-readable medium having instructions stored thereon, that, if executed by the processor, cause the processor to render a graphical user interface (GUI) for a cash in center on the display, the cash in center comprising a header portion, a confirmed cash in portion, an un-confirmed cash in portion, and a plurality of selectable UI elements operable to receive selections of one or more past, present, and future time periods and to display, add, edit, delete, and project cash in transactions for selected time periods, the instructions comprising: instructions for displaying, in the header portion, a current available balance for the one or more financial accounts, an account selector UI element, an add cash in UI element, a customer list UI element, and a receivable history UI element; instructions for displaying, in the unconfirmed cash in portion, data fields for unconfirmed cash in transactions for a selected time period of a plurality of time periods and a total value of the unconfirmed cash in transactions for the selected time period; instructions for displaying, in the confirmed cash in portion, data fields for confirmed cash in transactions for a selected time period of the plurality of time periods and a total value of the confirmed cash in transactions for the selected time period; instructions for displaying a cash reserve that is set as a value relative to at least one of the current available balances for the one or more financial accounts, the cash reserve being tunable by activation of a cash reserve adjuster UI element, wherein the cash reserve adjuster UI element enables setting the cash reserve to vary based on recurring, scheduled, or committed cash in transactions and/or recurring, scheduled, or committed cash out transactions; and instructions for setting the cash reserve separately for each of the selected time periods. 2. The system of claim 1 , wherein: the data fields for unconfirmed and confirmed cash in transactions are selectable and comprise a delete UI element, a due date, a customer, and an amount; the data fields for unconfirmed cash in transactions further comprise one or more of an expected date, a Confirm UI element, and a status UI element indicating unconfirmed; and the data fields for confirmed cash in transactions further comprise one or more of a received date, a category, and a status UI element indicating confirmed. 3. The system of claim 2 , the instructions further comprising: instructions for detecting a selection of a cash in transaction data field by determining that an input device has selected or hovered over a portion of the display where the data field is displayed; instructions for deleting a cash in transaction in response to detecting a selection of the delete UI element; instructions for rendering, in the display, an edit receivable interface in response to detecting a selection of a data field of a cash in transaction that is not the Confirm UI element or the delete UI element, the edit receivable interface comprising a plurality of editable data fields for the cash in transaction; instructions for rendering, in the display, a Confirm cash in interface in response to receiving a selection of the Confirm UI element for an unconfirmed cash in transaction, the Confirm cash in interface comprising a plurality of selectable confirming UI elements operable to unconfirm cash in transactions or set their status to confirmed. 4. The system of claim 3 , wherein a plurality of unconfirming UI elements comprise the delete UI element, an edit receivable UI element, the instructions further comprising: instructions for deleting the unconfirmed cash in transaction in response to receiving a selection of the delete UI element; and instructions for rendering, on the display, the edit receivable interface in response to receiving a selection of the edit receivable UI element. 5. The system of claim 3 , wherein the plurality of editable data fields in the edit receivable interface comprise a customer, an amount, a due date, a transaction date, and a recurring receivable selector. 6. The system of claim 5 , the instructions further comprising instructions to display recurrence conditions UI elements in the edit receivable interface in response to receiving a selection of the recurring receivable selector, wherein the recurrence conditions UI elements comprise a receivable frequency field, an indefinite recurrence button, a finite number of receivables field, and a date of a final receivable field, wherein the receivable frequency can be daily, weekly, monthly, and selectable portions or aggregations thereof. 7. The system of claim 6 , the instructions further comprising instructions for disabling the recurrence conditions UI elements in response to receiving a de-selection of the recurring receivable selector. 8. The system of claim 1 , the instructions further comprising: instructions for rendering, on the display, a customer list interface in response to receiving a selection of the customer list UI element, the customer list interface comprising an add customer button and a plurality of selectable customer names; instructions for rendering, on the display, an edit customer interface in response to receiving a selection of a customer name; and instructions for rendering, on the display, an add customer interface in response to receiving a selection of the add customer button, wherein the edit and add customer interfaces comprise editable customer data fields including customer name and one or more of customer address, receivable accounts, past customer payment methods, preferred payment method(s), late payment history, customer phone number, customer fax number, and customer email address. 9. The system of claim 1 , the instructions further comprising: instructions for rendering, on the display, an add cash in interface in response to receiving a selection of the add cash in UI element, wherein the add cash in interface includes the customer list interface and comprises a plurality of selectable cash in UI elements including a receivable source operable to select one of the one or more financial accounts and a customer account operable to display accounts associated with the customer for the cash in transaction and/or past cash in transactions. 10. The system of claim 1 , wherein the one or more financial accounts are associated with an entity and the cash in center is a cash in center of the entity. 11. The system of claim 1 , the instructions further comprising: in response to receiving a selection of one or more time periods for projected receivables, instructions for displaying, in the unconfirmed cash in portion, data fields for unconfirmed cash in transactions for the selected time periods; and in response to receiving a selection of one or more time periods for confirmed cash in transactions, instructions for displaying, in the confirmed cash in portion, data fields for unconfirmed cash in transactions for the selected time periods, wherein: for selected time periods in the past, the data fields for the cash in transactions indicate historical, posted transactions that have been paid by a customer or other payor; for a selected current time period, the data fields for the cash in transactions indicate information for transactions that have a status of confirmed and/or have a received date, due date, or transaction date in the current time period; for selected time periods in the future, the data fields for the cash in transactions ind
Accounting · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.