Patent Application
20180032978
Currently, several personal financial management and bill payment systems are available to help a personal financial management and bill payment system user, or any authorized party acting on behalf of a personal financial management and bill payment system user, obtain financial transaction data representing financial transactions conducted by the user, process/analyze the financial transaction data, display categorized financial transaction data, generate financial transaction reports, generate bills due and payment due reports, and/or make manual, semi-automated, and/or automatic bill payments through the personal financial management and bill payment system.
Some personal financial management and bill payment systems help users manage their finances and/or track their expenditures/financial transactions by providing a centralized interface with banks, credit card companies, and various other financial institutions, for electronically identifying and categorizing the user's financial transaction data. Currently, personal financial management and bill payment systems typically obtain electronic financial transaction data, such as payee data, payment amount data, transaction date data, etc. via communication with banks, credit card providers, or other financial institutions, using electronic data transfer systems, or various other systems for obtaining/transferring financial transaction data.
Personal financial management and bill payment systems have proven to be very popular and valuable tools for the users of the personal financial management and bill payment systems. This is largely due to the fact that using a personal financial management and bill payment system, a user can obtain most, if not all, of their financial transaction data from multiple sources and this data can be processed and analyzed in its entirety to create in depth, and very complete reports and features. Some personal financial management and bill payment systems include a payment due report/display generation feature. Typically, a payment due report includes personal financial management and bill payment system payment due data representing a listing of payments due, e.g., bill payment due items, within a defined period of time, such as a month, which require the user's attention.
In some cases, the user of the personal financial management and bill payment system is also provided the capability to make the listed payments on a manual, semi-automatic, i.e., with user approval, or automatic, basis.
Users of personal financial management and bill payment systems have come to rely on these payment due reports and often use the reports, and payment features, to pay the vast majority of their bills through the personal financial management and bill payment system. However, there remain several issues that are associated with currently available personal financial management and bill payment systems.
First, currently available personal financial management and bill payment systems do not provide a mechanism for automatically identifying, or distinguishing, invoices, invoice related financial transaction data, and/or invoice payments from bill payment data and then properly processing and integrating identified invoice related financial transaction data into the personal financial management and bill payment system as an invoice related payment due items.
As used herein, the term “bill” includes, but is not limited to, an account statement or other potentially recurring cost and financial transaction. Currently, bill payments due are represented in personal financial management and bill payment system payment due data. Examples of bills include, but are not limited to: rent payments, utility payments, credit card payments, grocery store payments, vehicle costs, etc. Bills are typically associated with larger, well known, and/or nationally or regionally known, payee businesses.
In contrast to the term “bill”, herein the term “invoice” includes, but is not limited to, documents/data associated with a specific product and/or service provided by a business and for which full payment is typically requested via a discrete invoice statement. Herein the term “invoice related financial transaction data” includes data representing all, or part of, an “invoice.” A given discrete invoice is therefore typically a non-recurring expense and/or is associated with specific products and/or services rendered, even though multiple, and even recurring identical, invoices can be generated by the same payee business for the same payor customer if multiple products and/or services, and/or the same products and/or services, are provided. Invoices are typically associated with smaller, regional or local, payee businesses than those associated with bills.
Herein the terms “payment,” and/or “payment due,” and/or “payment due items” are used interchangeably and include any payment owed by a first party, i.e., payor party, to a second party, i.e., a payee party. Consequently, as used herein, the terms “payment” and/or “payment due” include both “bills” and “invoices.”
One side effect of the popularity of payment due reports and the bill payment features offered through some personal financial management and bill payment systems is that any payment due items not included in the payment due reports, and/or not capable of being paid through the bill payment feature of the personal financial management and bill payment systems, are often forgotten, or at least treated as secondary, by the users of the personal financial management and bill payment systems. In short, as users of personal financial management and bill payment systems come to rely on the payment due reports listing payment due items and the bill payment features offered through some personal financial management and bill payment systems, they may forget, or neglect, any payments, such as invoice payments, that are not included in the payment due reports and payment due item listings and/or can't be paid through a bill payment feature of currently available personal financial management and bill payment systems.
This represents a significant and long standing technical problem in the financial management system, payment processing, and invoicing arts. This is because currently available personal financial management and bill payment systems process financial transaction data and generate personal financial management and bill payment system payment due data largely associated with recurring payments and/or revolving accounts, i.e., bills, such as credit card accounts, that can be identified through analysis of the users' financial transaction data history. In particular, currently available personal financial management and bill payment systems only identify recurring bills for inclusion in personal financial management and bill payment system payment due data and the payment due item listings of payment due reports, and/or other reminders of payments due, that are ultimately provided to the users of the personal financial management and bill payment systems. As a result, currently, one time only payments due, or non-revolving accounts, such as invoices, are almost never identified or included in the personal financial management and bill payment system payment due data and/or payment due item listings of payment due reports generated by personal financial management and bill payment systems.
As a result of the situation described above, smaller, local or regional, businesses generating invoices for their customers must currently rely on delivering their invoices to the customers through secondary, i.e., non-personal financial management and bill payment systems, mechanisms, and/or processes, such as e-mail or postal service. This, in turn, often leads to a situation where the invoicing business has trouble getting invoices in front of their customers, and/or getting their customers' attention, and/or integrating their invoices into the customers' payment routine, and/or getting paid. This situation exists today despite the fact that most businesses are business users of sophisticated business invoicing systems and/or business financial management systems that include business invoicing features.
Consequently, there is a long standing technical problem in the financial management system, payment processing, and invoicing arts in that businesses are currently unable to access personal financial management and bill payment systems used by their customers and provide invoices to their customers through the personal financial management and bill payment systems used by their customers as invoice related payment due items.
In addition, currently, when invoice related financial transaction data is entered manually by users of bill payment features offered through a personal financial management and bill payment system, that is, by simply entering payee data, amount data, routing data, and payment date data, a given payment is typically not identified as a payment associated with an invoice, as opposed a bill. In addition, financial transaction data obtained by, or through, a personal financial management and bill payment system often includes financial transaction data representing financial transactions performed by, or on behalf, of a user through another entity such as another financial institution account. Often, this financial transaction data also fails to indicate whether a given payment is associated with a bill or with an invoice.
Consequently, users of personal financial management and bill payment systems can pay either bills or invoices without designating which type of payment is being made. This is unfortunate given the differences between “bills” and “invoices.” in terms of how these two types of payments should ideally be identified, categorized, and processed by the personal financial management and bill payment system. In short, it would be very beneficial to identify any invoices and, once identified, provide a feature whereby identified invoices generated by a business invoicing system, and/or one or more financial institutions providing financial transaction data to the personal financial management and bill payment system, could be identified and then properly processed and integrated into the personal financial management and bill payment system as an invoice payment due item.
As a result there is also a long standing technical problem in the financial management system, payment processing, and invoicing arts in that currently available personal financial management and bill payment systems do not provide a mechanism for automatically identifying, or distinguishing, invoices, invoice data, and/or invoice payments and then properly processing and integrating identified invoices into a personal financial management and bill payment system as an invoice related payment due item.
Another issue associated with currently available personal financial management and bill payment systems is that each time a discrete transfer of funds is made, i.e., a funds transfer transaction is conducted, by, or through, a personal financial management and bill payment system, a funds transfer fee is typically charged by a financial institution providing the funds and/or the provider of the personal financial management and bill payment system. This funds transfer fee is typically charged to the payor business receiving the funds as payment from a payee user of the personal financial management and bill payment system, and/or the payee user of the personal financial management and bill payment system providing payment to the payor business, and/or the personal financial management and bill payment system facilitating the funds transfer from the payee user of the personal financial management and bill payment system to the payor business. Consequently, it is highly desirable that the number of funds transfer transactions conducted through the personal financial management and bill payment system be minimized for all parties involved.
However, since businesses are currently unable to access personal financial management and bill payment systems used by their customers and provide invoices to their customers through the personal financial management and bill payment systems used by their customers as payment due items, and currently available personal financial management and bill payment systems do not provide a mechanism for automatically identifying, or distinguishing, invoices, invoice related financial transaction data, and/or invoice payments or properly processing and integrating invoices into a personal financial management and bill payment system as an invoice related payment due item, invoices are either paid individually by mechanisms outside the personal financial management and bill payment system or, even if the invoice related financial transaction data is manually entered, or otherwise provided to/obtained by, the personal financial management and bill payment system, each discrete invoice is presented as a discrete payment due, and is paid individually, even when multiple invoices are directed to the same payor user by the same payee business. Consequently, currently, a discrete invoice payment funds transfer is made, and therefore a discrete invoice payment funds transfer charge is incurred, each time an invoice payment is made from a discrete payor user of the personal financial management and bill payment system to a given payee business, even when each of the discrete invoice payments are made to the same given payee business and, in some cases, even when each of the discrete invoice payments is made to the same given payee business by the same payor user of the personal financial management and bill payment system.
As a result, currently, numerous funds transfer charges are incurred in the form of discrete invoice payment funds transfer charges associated with invoice payments made to the same payee business through personal financial management and bill payment systems. This clearly represents an inefficient use of resources and a significant, largely unnecessary, cost to the parties involved
In addition, since currently, each invoice payment made from a discrete payor user of the personal financial management and bill payment system to a given payee business is processed as an individual and discrete funds transfer transaction, even when each of the discrete invoice payments are made to the same given payee business and, in some cases, even when each of the discrete invoice payments is made to the same given payee business by the same payor user of the personal financial management and bill payment system, human and non-human resources, processing power and processor cycles, memory, and communications bandwidth are inefficiently utilized to process numerous discrete funds transfers representing invoice payments made to the same given payee business by multiple payor users of a personal financial management and bill payment system. This also clearly represents an inefficient allocation of resources.
Consequently, there is a long standing technical problem in the payment processing, invoice processing and financial management arts of providing for automatic integration of invoice related financial transaction data into a personal financial management and bill payment system and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
What is needed is a method and system for automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system. In this way, invoices represented in invoice related financial transaction data could be processed by the personal financial management and bill payment system at minimal cost to the parties involved, using minimal resources, and in a seamless and effective manner.
In accordance with one embodiment, invoice related financial transaction data is obtained and integrated into a personal financial management and bill payment system. Then, all requested invoice payments associated with invoices represented in the invoice related financial transaction data having the same payee business are identified and aggregated.
In one embodiment, the amounts of the aggregated requested invoice payments for the payee business are then summed to determine the total amount to be transferred to the payee business and this total amount to be transferred to the payee business is then processed as a single funds transfer item by the personal financial management and bill payment system.
Consequently, using the disclosed embodiments, invoices represented in invoice related financial transaction data can be integrated into, and processed by, the personal financial management and bill payment system at minimal cost to the parties involved, using minimal resources, and in a seamless and effective manner.
Therefore, the disclosed embodiments provide an efficient, effective, and highly adaptable solution to the long standing technical problem in the bill payment, invoice processing, and financial management arts of automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
In accordance with one embodiment of a method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction, access to invoice related financial transaction data generated by the one or more payee businesses is obtained.
In one embodiment, the invoice related financial transaction data represents two or more discrete invoices submitted by one or more payee businesses requesting payment by one or more payor users of the personal financial management and bill payment system.
In one embodiment, the invoice related financial transaction data includes payee business identity data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the payee business identity data represents the identity of the payee business associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, the invoice related financial transaction data also includes payor user identity data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the payor user identity data represents the identity of the payor user associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, the invoice related financial transaction data further includes invoice amount data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the invoice amount data represents the payment amount associated with each discrete invoice represented in the invoice related financial transaction data.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system. In one embodiment, the personal financial management and bill payment system payment due data represents one or more payments due associated with one or more users of the personal financial management and bill payment system as payment due items to be paid through the personal financial management and bill payment system.
In accordance with one embodiment, invoice payment request data is received from one or more users of the personal financial management and bill payment system. In one embodiment, the invoice payment request data represents one or more requests from one or more users of the personal financial management and bill payment system to pay one or more requested invoice payment amounts associated with one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data through the personal financial management and bill payment system.
In accordance with one embodiment, access to the personal financial management and bill payment system and the personal financial management and bill payment system payment due data, including the integrated invoice related financial transaction data, and the invoice payment request data is obtained.
In accordance with one embodiment, the invoice payment request data is analyzed to identify discrete invoice payment request related invoice data representing one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data.
In accordance with one embodiment, the integrated invoice related financial transaction data associated with the discrete invoice payment request related invoices is analyzed to identify the payee business identity data associated with each discrete invoice payment request related invoice represented in the discrete invoice payment request related invoice data.
In accordance with one embodiment, a first payee business represented in the payee business identity data associated with two or more discrete first payee business invoice payment request related invoices represented in the discrete invoice payment request related invoice data is identified.
In accordance with one embodiment, all the invoice related financial transaction data associated with the two or more discrete invoice payment request related invoices is aggregated to generate aggregated first payee business invoice payment request invoice data.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data is analyzed to identify the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices.
In accordance with one embodiment, the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices is processed and summed to generate aggregated total first payee business invoice payment amount data representing a total requested invoice payment amount for the first payee business as requested by two or more users of the personal financial management and bill payment system.
In accordance with one embodiment, the aggregated total first payee business invoice payment amount data is then processed as a single first payee business funds transfer item using the personal financial management and bill payment system.
The disclosed embodiments provide an efficient, effective, and highly adaptable solution to the long standing technical problem in the bill payment, invoice processing, and financial management arts of automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
However, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction does not encompass, embody, or preclude other forms of innovation in the area of automated financial transaction bill payment processing and invoicing. In addition, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is not related to any fundamental economic practice, fundamental data processing practice, mental steps, or pen and paper based solution. In fact, the disclosed embodiments are directed to providing solutions to the relatively new problems associated with the automatic processing and display of electronic financial transaction data obtained from multiple sources, making electronic bill payments, and the management and processing of large amounts of data, i.e., “big data.” Consequently, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is not directed to, does not encompass, and is not merely, an abstract idea or concept.
In addition, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for significant improvements to the technical fields of electronic transaction data processing, invoicing, financial transaction categorization, information dissemination, data processing, data management, data filtering and mining, automatic electronic bill payment, and user experience.
In addition, by allowing for the integration of invoices and invoice data into a personal financial management and bill payment system, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction helps users of the personal financial management and bill payment system identify and pay their invoices. This, in turn, helps avoid the reissuance and repeated transmission of payment due reminders and for the entry, processing, and dissemination, of redundant invoice data; thereby eliminating unnecessary data analysis before resources are allocated to processing, and/or correcting, redundant reminder data and the redundant reminder data is further transmitted/distributed.
Consequently, using the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction results in more efficient use of human and non-human resources, fewer processor cycles being utilized, reduced memory utilization, and less communications bandwidth being utilized to relay data to, and from, backend systems and client systems.
As a result, computing systems are transformed into faster, more efficient, and more effective computing systems by implementing the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction.
In addition, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for the entry, processing, and dissemination, of only relevant portions of data; thereby eliminating unnecessary data analysis and correction before resources are allocated to processing, and/or correcting, faulty/irrelevant data, and/or the faulty/irrelevant data is further transmitted/distributed.
In addition, by aggregating requested invoice payment amounts associated with multiple invoices represented in the invoice related financial transaction data having the same payee business into single funds transfer item, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for the processing and dissemination of invoice related financial transaction data representing multiple discrete invoices as a single funds transfer entity/object. This, in turn, helps avoid the processing and transmission of multiple individual invoice payment related data sets and related funds transfer transaction data sets.
Consequently, using the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction results in more efficient use of human and non-human resources, fewer processor cycles being utilized, reduced memory utilization, and less communications bandwidth being utilized to relay data to, and from, backend systems and client systems.
As a result, computing systems are transformed into faster, more efficient, and more effective computing systems by implementing the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction.
Common reference numerals are used throughout the FIG.s and the detailed description to indicate like elements. One skilled in the art will readily recognize that the above FIG.s are examples and that other architectures, modes of operation, orders of operation, and elements/functions can be provided and implemented without departing from the characteristics and features of the invention, as set forth in the claims.
Herein, the term “personal financial management and bill payment system” includes, but is not limited to, the following: computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal financial transaction aggregation and/or processing systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal financial management and budgeting systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal data management systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal accounting systems, services, packages, programs, modules, or applications; personal electronic tax preparation systems, services, packages, programs, modules, or applications; and various other personal electronic data management systems, services, packages, programs, modules, or applications, whether known at the time of filling, or as developed later.
Specific examples of personal financial management and bill payment systems include, but are not limited to the following: Mint™, available from Intuit, Inc. of Mountain View, Calif.; Mint Online™, available from Intuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit, Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit, Inc. of Mountain View, Calif.; and/or various other software systems discussed herein, and/or known to those of skill in the art at the time of filing, and/or as developed after the time of filing.
Herein, the term “business invoicing system” includes, but is not limited to, any system through which a business can generate, and/or submit, and/or process invoices requesting payment for products and/or services provided by the business to customers of the business. Therefore, the term “business invoicing system” includes, but is not limited to, the following: computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business accounting and/or invoicing systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business financial transaction aggregation and/or processing systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business financial management and budgeting systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business management systems, services, packages, programs, modules, or applications; business electronic tax preparation systems, services, packages, programs, modules, or applications; and various other business electronic data management systems, services, packages, programs, modules, or applications, whether known at the time of filling, or as developed later.
Specific examples of “business invoicing systems” include, but are not limited to, the following: QuickBooks™, available from Intuit, Inc. of Mountain View, Calif.; QuickBooks Online™, available from Intuit, Inc. of Mountain View, Calif.; QuickBooks Self-Employed™, available from Intuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit, Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit, Inc. of Mountain View, Calif.; and/or various other software systems discussed herein, and/or known to those of skill in the art at the time of filing, and/or as developed after the time of filing.
Herein, the terms “software system” and “software application” are used interchangeably and can be, but are not limited to, any data management system implemented on a computing system, accessed through one or more servers, accessed through a network, accessed through a cloud, and/or provided through any system or by any mechanism and/or process, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing, that gathers/obtains data, from one or more sources and/or has the capability to analyze at least part of the data.
As used herein, the terms “computing system,” “computing device,” and “computing entity,” include, but are not limited to, the following: a server computing system; a workstation; a desktop computing system; a mobile computing system, including, but not limited to, smart phones, portable devices, and/or devices worn or carried by a user; a database system or storage cluster; a virtual asset; a switching system; a router; any hardware system; any communications system; any form of proxy system; a gateway system; a firewall system; a load balancing system; or any device, subsystem, or mechanism that includes components that can execute all, or part, of any one of the processes and/or operations as described herein.
In addition, as used herein, the terms “computing system” and “computing entity,” can denote, but are not limited to the following: systems made up of multiple virtual assets, server computing systems, workstations, desktop computing systems, mobile computing systems, database systems or storage clusters, switching systems, routers, hardware systems, communications systems, proxy systems, gateway systems, firewall systems, load balancing systems, or any devices that can be used to perform the processes and/or operations as described herein.
Herein, the terms “mobile computing system” and “mobile device” are used interchangeably and include, but are not limited to the following: a smart phone; a cellular phone; a digital wireless telephone; a tablet computing system; a notebook computing system; any portable computing system; a two-way pager; a Personal Digital Assistant (PDA); a media player; an Internet appliance; devices worn or carried by a user; or any other movable/mobile device and/or computing system that includes components that can execute all, or part, of any one of the processes and/or operations as described herein.
Herein, the term “production environment” includes the various components, or assets, used to deploy, implement, access, and use, a given software system as that software system is intended to be used. In various embodiments, production environments include multiple computing systems and/or assets that are combined, communicatively coupled, virtually and/or physically connected, and/or associated with one another, to provide the production environment implementing the application.
As specific illustrative examples, the assets making up a given production environment can include, but are not limited to, the following: one or more computing environments used to implement at least part of the software system in the production environment such as a data center, a cloud computing environment, a dedicated hosting environment, and/or one or more other computing environments in which one or more assets used by the application in the production environment are implemented; one or more computing systems or computing entities used to implement at least part of the software system in the production environment; one or more virtual assets used to implement at least part of the software system in the production environment; one or more supervisory or control systems, such as hypervisors, or other monitoring and management systems used to monitor and control assets and/or components of the production environment; one or more communications channels for sending and receiving data used to implement at least part of the software system in the production environment; one or more access control systems for limiting access to various components of the production environment, such as firewalls and gateways; one or more traffic and/or routing systems used to direct, control, and/or buffer data traffic to components of the production environment, such as routers and switches; one or more communications endpoint proxy systems used to buffer, process, and/or direct data traffic, such as load balancers or buffers; one or more secure communication protocols and/or endpoints used to encrypt/decrypt data, such as Secure Sockets Layer (SSL) protocols, used to implement at least part of the software system in the production environment; one or more databases used to store data in the production environment; one or more internal or external services used to implement at least part of the software system in the production environment; one or more backend systems, such as backend servers or other hardware used to process data and implement at least part of the software system in the production environment; one or more software modules/functions used to implement at least part of the software system in the production environment; and/or any other assets/components making up an actual production environment in which at least part of the software system is deployed, implemented, accessed, and run, e.g., operated, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing.
As used herein, the term “computing environment” includes, but is not limited to, a logical or physical grouping of connected or networked computing systems and/or virtual assets using the same infrastructure and systems such as, but not limited to, hardware systems, software systems, and networking/communications systems. Typically, computing environments are either known, “trusted” environments or unknown, “untrusted” environments. Typically, trusted computing environments are those where the assets, infrastructure, communication and networking systems, and security systems associated with the computing systems and/or virtual assets making up the trusted computing environment, are either under the control of, or known to, a party.
In various embodiments, each computing environment includes allocated assets and virtual assets associated with, and controlled or used to create, and/or deploy, and/or operate at least part of the software system.
In various embodiments, one or more cloud computing environments are used to create, and/or deploy, and/or operate at least part of the software system that can be any form of cloud computing environment, such as, but not limited to, a public cloud; a private cloud; a virtual private network (VPN); a subnet; a Virtual Private Cloud (VPC); a sub-net or any security/communications grouping; or any other cloud-based infrastructure, sub-structure, or architecture, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing.
In many cases, a given software system or service may utilize, and interface with, multiple cloud computing environments, such as multiple VPCs, in the course of being created, and/or deployed, and/or operated.
As used herein, the term “virtual asset” includes any virtualized entity or resource, and/or virtualized part of an actual, or “bare metal” entity. In various embodiments, the virtual assets can be, but are not limited to, the following: virtual machines, virtual servers, and instances implemented in a cloud computing environment; databases associated with a cloud computing environment, and/or implemented in a cloud computing environment; services associated with, and/or delivered through, a cloud computing environment; communications systems used with, part of, or provided through a cloud computing environment; and/or any other virtualized assets and/or sub-systems of “bare metal” physical devices such as mobile devices, remote sensors, laptops, desktops, point-of-sale devices, etc., located within a data center, within a cloud computing environment, and/or any other physical or logical location, as discussed herein, and/or as known/available in the art at the time of filing, and/or as developed/made available after the time of filing.
In various embodiments, any, or all, of the assets making up a given production environment discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing can be implemented as one or more virtual assets.
In one embodiment, two or more assets, such as computing systems and/or virtual assets, and/or two or more computing environments are connected by one or more communications channels including but not limited to, Secure Sockets Layer (SSL) communications channels and various other secure communications channels, and/or distributed computing system networks, such as, but not limited to the following: a public cloud; a private cloud; a virtual private network (VPN); a subnet; any general network, communications network, or general network/communications network system; a combination of different network types; a public network; a private network; a satellite network; a cable network; or any other network capable of allowing communication between two or more assets, computing systems, and/or virtual assets, as discussed herein, and/or available or known at the time of filing, and/or as developed after the time of filing.
As used herein, the term “network” includes, but is not limited to, any network or network system such as, but not limited to, the following: a peer-to-peer network; a hybrid peer-to-peer network; a Local Area Network (LAN); a Wide Area Network (WAN); a public network, such as the Internet; a private network; a cellular network; any general network, communications network, or general network/communications network system; a wireless network; a wired network; a wireless and wired combination network; a satellite network; a cable network; any combination of different network types; or any other system capable of allowing communication between two or more assets, virtual assets, and/or computing systems, whether available or known at the time of filing or as later developed.
Herein, the term “party,” “user,” “user consumer,” and “customer” are used interchangeably to denote any party and/or entity that interfaces with, and/or to whom information is provided by, the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction described herein, and/or a person and/or entity that interfaces with, and/or to whom information is provided by, the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction described herein, and/or a legal guardian of person and/or entity that interfaces with, and/or to whom information is provided by, the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction described herein, and/or an authorized agent of any party and/or person and/or entity that interfaces with, and/or to whom information is provided by, the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction described herein. For instance, in various embodiments, a user can be, but is not limited to, a person, a commercial entity, an application, a service, and/or a computing system.
Herein, the term “financial transaction” includes, but is not limited to, any interaction between two or more parties involving the transfer, or re-categorization, of funds between the parties. Herein, the term “financial transaction data” includes, but is not limited to, electronic data representing at least one financial transaction and that is capable of being processed by a processor, and/or stored in a memory, and/or is otherwise machine readable.
Herein, the term “product and/or service provider” includes any party and/or entity that is associated with a user through a financial transaction represented by financial transaction data.
As used herein, the term “bill” includes, but is not limited to, an account statement or other potentially recurring cost and financial transaction. Currently, bill payments due are represented in personal financial management and bill payment system payment due data. Examples of bills include, but are not limited to: rent payments, utility payments, credit card payments, grocery store payments, vehicle costs, etc. Bills are typically associated with larger, well known, and/or nationally or regionally known, payee businesses.
In contrast to the term “bill”, herein the term “invoice” includes, but is not limited to, documents/data associated with a specific product and/or service provided by a business and for which full payment is typically requested via a discrete invoice statement. Herein the term “invoice related financial transaction data” includes data representing all, or part of, an “invoice.” A given discrete invoice is therefore typically a non-recurring expense and/or is associated with specific products and/or services rendered, even though multiple, and even recurring identical, invoices can be generated by the same payee business for the same payor customer if multiple products and/or services, and/or the same products and/or services, are provided. Invoices are typically associated with smaller, regional or local, payee businesses than those associated with bills.
Herein the terms “payment,” and/or “payment due,” and/or “payment due items” are used interchangeably and include any payment owed by a first party, i.e., payor party, to a second party, i.e., a payee party. Consequently, as used herein, the terms “payment” and/or “payment due” include both “bills” and “invoices.”
As used herein, the term “payor user” includes any user of a personal financial management and bill payment system associated with an invoice included in invoice related financial transaction data and to whom the invoice related financial transaction data is directed by a payee business.
As used herein, the term “payee business” includes any party or entity associated with an invoice included in invoice related financial transaction data and to whom the invoice amount associated with in invoice represented in invoice related financial transaction data is owed by a payor user.
Embodiments will now be discussed with reference to the accompanying FIG.s, which depict one or more exemplary embodiments. Embodiments may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein, shown in the FIG.s, and/or described below. Rather, these exemplary embodiments are provided to allow a complete disclosure that conveys the principles of the invention, as set forth in the claims, to those of skill in the art.
In accordance with one embodiment of a method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction, access to invoice related financial transaction data generated by the one or more payee businesses is obtained.
In one embodiment, the obtained invoice related financial transaction data represents two or more discrete invoices submitted by one or more payee businesses requesting payment by one or more payor users of the personal financial management and bill payment system.
In one embodiment, the invoice related financial transaction data includes payee business identity data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the payee business identity data represents the identity of the payee business associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, the invoice related financial transaction data also includes payor user identity data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the payor user identity data represents the identity of the payor user associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, the invoice related financial transaction data further includes invoice amount data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the invoice amount data represents the payment amount associated with each discrete invoice represented in the invoice related financial transaction data.
In accordance with one embodiment, the invoice related financial transaction data generated by the one or more payee businesses is obtained from a business invoicing system provided to business users of the business invoicing system.
As noted above, herein, the term “business invoicing system” includes, but is not limited to, any system through which a business can generate, and/or submit, and/or process invoices requesting payment for products and/or services provided by the business to customers of the business. Therefore, the term “business invoicing system” includes, but is not limited to, the following: computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business accounting and/or invoicing systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business financial transaction aggregation and/or processing systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business financial management and budgeting systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, business management systems, services, packages, programs, modules, or applications; business electronic tax preparation systems, services, packages, programs, modules, or applications; and various other business electronic data management systems, services, packages, programs, modules, or applications, whether known at the time of filling, or as developed later.
Specific examples of “business invoicing systems” include, but are not limited to, the following: QuickBooks™, available from Intuit, Inc. of Mountain View, Calif.; QuickBooks Online™, available from Intuit, Inc. of Mountain View, Calif.; QuickBooks Self-Employed™, available from Intuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit, Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit, Inc. of Mountain View, Calif.; and/or various other software systems discussed herein, and/or known to those of skill in the art at the time of filing, and/or as developed after the time of filing.
In some embodiments, the business invoicing system is part of, and/or a feature of, a parent small business financial management system.
In one embodiment, a personal financial management and bill payment system is provided using one or more computing systems.
As noted above, herein, the term “personal financial management and bill payment system” includes, but is not limited to, the following: computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal financial transaction aggregation and/or processing systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal financial management and budgeting systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal data management systems, services, packages, programs, modules, or applications; computing system, desktop system, mobile system, and/or wearable device implemented, and/or online, and/or web-based, storage based, persistence based, personal accounting systems, services, packages, programs, modules, or applications; personal electronic tax preparation systems, services, packages, programs, modules, or applications; and various other personal electronic data management systems, services, packages, programs, modules, or applications, whether known at the time of filling, or as developed later.
As noted above, specific examples of personal financial management and bill payment systems include, but are not limited to the following: Mint™, available from Intuit, Inc. of Mountain View, Calif.; Mint Online™, available from Intuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit, Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit, Inc. of Mountain View, Calif.; and/or various other software systems discussed herein, and/or known to those of skill in the art at the time of filing, and/or as developed after the time of filing.
Currently, personal financial management and bill payment systems and business invoicing systems are typically distinct software systems operated and/or used by two distinct parties, e.g., a customer of a business and an owner of a business, respectively. Therefore, currently, personal financial management and bill payment systems and business invoicing systems typically operate in isolation from each other, even when they are offered by the same personal financial management and bill payment system and business invoicing system provider.
As a specific illustrative example, in one embodiment, the personal financial management and bill payment system used by a customer of a business, or other user, could be a personal financial transaction management system such as Mint™, available from Intuit, Inc. of Mountain View, Calif. In this specific illustrative example, a business invoicing system, used by a business user, could be a business invoicing system such as QuickBooks™, available from Intuit, Inc. of Mountain View, Calif. As seen in this specific illustrative example, both the personal financial management and bill payment system and the business invoicing system are offered by the same software system provider, i.e., in this specific case, Intuit, Inc. of Mountain View, Calif. Consequently, according to one embodiment, in this specific illustrative example, the personal financial management and bill payment system and the business invoicing system are provided the opportunity to cross pollinate and cross confirm supported data. This approach has several unique advantages.
In accordance with one embodiment, one or more processors associated with one or more computing systems are utilized to obtain access to the business invoicing system and obtain invoice related financial transaction data generated by the one or more payee businesses.
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses includes, but is not limited to:
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses includes, but is not limited to:
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses includes, but is not limited to:
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses includes any method, system, process and/or procedure for obtaining access to invoice related financial transaction data generated by the one or more payee businesses as discussed herein, known in the art at the time of filing, and/or as developed/made available after the time of filing.
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses includes any method, system, process and/or procedure for obtaining access to invoice related financial transaction data generated by the one or more payee businesses as discussed in: U.S. patent application Ser. No. 15/140,117 (docket number INTU169676), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/140,131 (docket number INTU169677), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/142,708 (docket number INTU169678), filed on behalf of the same Inventors of the present patent application, filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system.
In one embodiment, the personal financial management and bill payment system payment due data represents one or more payments due associated with one or more users of the personal financial management and bill payment system as payment due items to be paid through the personal financial management and bill payment system.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system by assigning a personal financial management and bill payment system financial transaction category to the discrete invoices represented in the invoice related financial transaction data.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system by providing the discrete invoices represented in the invoice related financial transaction data as line items in a payment due item listing generated through the personal financial management and bill payment system.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system by assigning a personal financial management and bill payment system financial transaction category to the discrete invoices represented in the invoice related financial transaction data.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system by any method, system, process and/or procedure for integrating invoice related financial transaction data into personal financial management and bill payment system payment due data as discussed herein, known in the art at the time of filing, and/or as developed/made available after the time of filing.
In accordance with various embodiments, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system by any method, system, process and/or procedure for integrating invoice related financial transaction data into personal financial management and bill payment system payment due data as discussed in: U.S. patent application Ser. No. 15/140,117 (docket number INTU169676), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/140,131 (docket number INTU169677), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/142,708 (docket number INTU169678), filed on behalf of the same Inventors of the present patent application, filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein.
In accordance with one embodiment, invoice payment request data is received from one or more users of the personal financial management and bill payment system.
As noted above, personal financial management and bill payment systems help a personal financial management and bill payment system user, or any authorized party acting on behalf of a personal financial management and bill payment system user, obtain financial transaction data representing financial transactions conducted by the user, process/analyze the financial transaction data, display categorized financial transaction data, generate financial transaction reports, generate bills due and payment due reports, and/or make manual, semi-automated, and/or automatic bill payments through the personal financial management and bill payment system.
As also noted above, some personal financial management and bill payment systems help users manage their finances and/or track their expenditures/financial transactions by providing a centralized interface with banks, credit card companies, and various other financial institutions, for electronically identifying and categorizing the user's financial transaction data. Currently, personal financial management and bill payment systems typically obtain electronic financial transaction data, such as payee data, payment amount data, transaction date data, etc. via communication with banks, credit card providers, or other financial institutions, using electronic data transfer systems, or various other systems for obtaining/transferring financial transaction data.
In addition, some personal financial management and bill payment systems include a payment due report/display generation feature. Typically, a payment due report includes personal financial management and bill payment system payment due data representing a listing of payments due, e.g., bill payment due items, within a defined period of time, such as a month, which require the user's attention.
As also noted above, in some cases, the users of the personal financial management and bill payment systems are also provided a bill payment service and the capability to make payments on a manual, semi-automatic, i.e., with user approval, or automatic, basis to various payees. In order to make these payments, the users of the personal financial management and bill payment systems typically enter data into the personal financial management and bill payment systems directing, or requesting, that one or more payments be made to one or more payees on a one-time, recurring, automatic, semi-automatic, or manual basis.
In the present embodiments, where invoice related financial transaction data has been integrated into the personal financial management and bill payment system payment due data, invoice payment requests are made by the users of the personal financial management and bill payment systems by entering, and/or providing, invoice payment request data.
In one embodiment, the invoice payment request data received by the personal financial management and bill payment system represents one or more requests from one or more users of the personal financial management and bill payment system to pay one or more requested invoice payment amounts associated with one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data through the personal financial management and bill payment system.
In accordance with one embodiment, access to the personal financial management and bill payment system and the personal financial management and bill payment system payment due data, including the integrated invoice related financial transaction data, and the invoice payment request data is obtained.
In accordance with one embodiment, one or more processors associated with one or more computing systems are utilized to obtain access to the personal financial management and bill payment system and the personal financial management and bill payment system payment due data, including the integrated invoice related financial transaction data, and the invoice payment request data.
In accordance with one embodiment, the invoice payment request data is analyzed by one or more processors associated with one or more computing systems to identify discrete invoice payment request related invoice data representing one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data.
In accordance with one embodiment, the integrated invoice related financial transaction data associated with the discrete invoice payment request related invoices is analyzed by one or more processors associated with one or more computing systems to identify the payee business identity data associated with each discrete invoice payment request related invoice represented in the discrete invoice payment request related invoice data.
In accordance with one embodiment, a first payee business represented in the payee business identity data associated with two or more discrete first payee business invoice payment request related invoices represented in the discrete invoice payment request related invoice data is identified by one or more processors associated with one or more computing systems.
In accordance with one embodiment, all the invoice related financial transaction data associated with the two or more discrete invoice payment request related invoices is aggregated by one or more processors associated with one or more computing systems to generate aggregated first payee business invoice payment request invoice data.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data is analyzed by one or more processors associated with one or more computing systems to identify the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices.
In accordance with one embodiment, the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices is processed and summed by one or more processors associated with one or more computing systems to generate aggregated total first payee business invoice payment amount data representing a total requested invoice payment amount for the first payee business requested by two or more users of the personal financial management and bill payment system.
In accordance with one embodiment, the aggregated total first payee business invoice payment amount data is then processed by one or more processors associated with one or more computing systems as a single first payee business funds transfer item using the personal financial management and bill payment system.
In accordance with one embodiment, processing the aggregated total first payee business invoice payment amount data as a single first payee business funds transfer item using the personal financial management and bill payment system includes providing the aggregated total first payee business invoice payment amount data as a line item in a funds transfer item listing generated through the personal financial management and bill payment system.
In accordance with one embodiment, processing the aggregated total first payee business invoice payment amount data as a single first payee business funds transfer item using the personal financial management and bill payment system includes applying one or more aggregated first payee business invoice payment request invoice data processing rules to the aggregated first payee business invoice payment request invoice data.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data processing rules include, but are not limited to, an aggregated first payee business invoice payment request invoice data processing rule limiting the aggregated total first payee business invoice payment amount to a threshold amount.
Using this aggregated first payee business invoice payment request invoice data processing rule, the financial risk associated with the single first payee business funds transfer transaction is limited to the threshold amount.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data processing rules include, but are not limited to, an aggregated first payee business invoice payment request invoice data processing rule limiting the total number of discrete invoices represented in the aggregated first payee business invoice payment request invoice data to a threshold number of discrete invoices.
Using this aggregated first payee business invoice payment request invoice data processing rule, the total liability associated with the single first payee business funds transfer transaction is limited to a total aggregated invoice amount associated with a threshold number of discrete invoices, thereby limiting the financial risk.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data processing rules include any of the aggregated first payee business invoice payment request invoice data processing rules desired, and/or as discussed herein, known in the art at the time of filing, and/or as developed/made available after the time of filing.
As seen in
As seen in
In one embodiment, personal financial management and bill payment system payment due data 113 represents one or more bills associated with one or more users (not shown) of personal financial management and bill payment system 111 to be paid through personal financial management and bill payment system 111. In one embodiment, personal financial management and bill payment system payment due data 113 includes data representing a payment due item listing (not shown).
As noted, in one embodiment, invoice payment request data 114 represents one or more requests from one or more users (not shown) of personal financial management and bill payment system 111 to pay one or more requested invoice payment amounts associated with one or more discrete invoice payment request related invoices represented in invoice related financial transaction data 123 through personal financial management and bill payment system 111.
As seen in
In one embodiment, invoice related financial transaction data 123 includes payee business identity data associated with each discrete invoice represented in the invoice related financial transaction data (not shown). In one embodiment, the payee business identity data represents the identity of the payee business associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, invoice related financial transaction data 123 also includes payor user identity data associated with each discrete invoice represented in the invoice related financial transaction data (not shown). In one embodiment, the payor user identity data represents the identity of the payor user associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, invoice related financial transaction data 123 further includes invoice amount data associated with each discrete invoice represented in the invoice related financial transaction data (not shown). In one embodiment, the invoice amount data represents the payment amount associated with each discrete invoice represented in the invoice related financial transaction data.
As seen in
As seen in
As seen in
As seen in
As seen in
As seen in
As seen in
As seen in
As seen in
The disclosed embodiments provide an efficient, effective, and highly adaptable solution to the long standing technical problem in the bill payment, invoice processing, and financial management arts of automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
However, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction does not encompass, embody, or preclude other forms of innovation in the area of automated financial transaction bill payment processing and invoicing. In addition, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is not related to any fundamental economic practice, fundamental data processing practice, mental steps, or pen and paper based solution. In fact, the disclosed embodiments are directed to providing solutions to the relatively new problems associated with the automatic processing and display of electronic financial transaction data obtained from multiple sources, making electronic bill payments, and the management and processing of large amounts of data, i.e., “big data.” Consequently, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is not directed to, does not encompass, and is not merely, an abstract idea or concept.
In addition, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for significant improvements to the technical fields of electronic transaction data processing, invoicing, financial transaction categorization, information dissemination, data processing, data management, data filtering and mining, automatic electronic bill payment, and user experience.
In addition, by allowing for the integration of invoices and invoice data into a personal financial management and bill payment system, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction helps users of the personal financial management and bill payment system identify and pay their invoices. This, in turn, helps avoid the reissuance and repeated transmission of payment due reminders and for the entry, processing, and dissemination, of redundant invoice data; thereby eliminating unnecessary data analysis before resources are allocated to processing, and/or correcting, redundant reminder data and the redundant reminder data is further transmitted/distributed.
Consequently, using the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction results in more efficient use of human and non-human resources, fewer processor cycles being utilized, reduced memory utilization, and less communications bandwidth being utilized to relay data to, and from, backend systems and client systems.
As a result, computing systems are transformed into faster, more efficient, and more effective computing systems by implementing the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction.
In addition, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for the entry, processing, and dissemination, of only relevant portions of data; thereby eliminating unnecessary data analysis and correction before resources are allocated to processing, and/or correcting, faulty/irrelevant data, and/or the faulty/irrelevant data is further transmitted/distributed.
In addition, by aggregating requested invoice payment amounts associated with multiple invoices represented in the invoice related financial transaction data having the same payee business into single funds transfer item, the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for the processing and dissemination of invoice related financial transaction data representing multiple discrete invoices as a single funds transfer entity/object. This, in turn, helps avoid the processing and transmission of multiple individual invoice payment related data sets and related funds transfer transaction data sets.
Consequently, using the disclosed method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction results in more efficient use of human and non-human resources, fewer processor cycles being utilized, reduced memory utilization, and less communications bandwidth being utilized to relay data to, and from, backend systems and client systems.
As a result, computing systems are transformed into faster, more efficient, and more effective computing systems by implementing the method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction.
In accordance with one embodiment, invoice related financial transaction data is obtained and integrated into a personal financial management and bill payment system. Then, all requested invoice payments associated with invoices represented in the invoice related financial transaction data having the same payee business are identified and aggregated.
In one embodiment, the amounts of the aggregated requested invoice payments for the payee business are then summed to determine the total amount to be transferred to the payee business and this total amount to be transferred to the payee business is then processed as a single funds transfer item by the personal financial management and bill payment system.
Consequently, using the disclosed embodiments, invoices represented in invoice related financial transaction data can be integrated into, and processed by, the personal financial management and bill payment system at minimal cost to the parties involved, using minimal resources, and in a seamless and effective manner.
Therefore, the disclosed embodiments provide an efficient, effective, and highly adaptable solution to the long standing technical problem in the bill payment, invoice processing, and financial management arts of automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
Consequently, using the disclosed embodiments, invoices represented in invoice related financial transaction data can be integrated into, and processed by, the personal financial management and bill payment system at minimal cost to the parties involved, using minimal resources, and in a seamless and effective manner.
Therefore, the disclosed embodiments provide an efficient, effective, and highly adaptable solution to the long standing technical problem in the bill payment, invoice processing, and financial management arts of automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
As seen in
In one embodiment, at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203, access to invoice related financial transaction data generated by the one or more payee businesses is obtained.
In one embodiment, the obtained invoice related financial transaction data of OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 represents two or more discrete invoices submitted by one or more payee businesses requesting payment by one or more payor users of the personal financial management and bill payment system.
In one embodiment, the invoice related financial transaction data of OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes payee business identity data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the payee business identity data represents the identity of the payee business associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, the invoice related financial transaction data of OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 also includes payor user identity data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the payor user identity data represents the identity of the payor user associated with each discrete invoice represented in the invoice related financial transaction data.
In one embodiment, the invoice related financial transaction data of OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 further includes invoice amount data associated with each discrete invoice represented in the invoice related financial transaction data. In one embodiment, the invoice amount data represents the payment amount associated with each discrete invoice represented in the invoice related financial transaction data.
In accordance with one embodiment, at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 the invoice related financial transaction data generated by the one or more payee businesses is obtained from a business invoicing system provided to business users of the business invoicing system.
In accordance with one embodiment, at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 one or more processors associated with one or more computing systems are utilized to obtain access to the business invoicing system and obtain invoice related financial transaction data generated by the one or more payee businesses.
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes, but is not limited to:
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes, but is not limited to:
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes, but is not limited to:
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes any method, system, process and/or procedure for obtaining access to invoice related financial transaction data generated by the one or more payee businesses as discussed herein, known in the art at the time of filing, and/or as developed/made available after the time of filing.
In accordance with one embodiment, obtaining access to invoice related financial transaction data generated by the one or more payee businesses at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes any method, system, process and/or procedure for obtaining access to invoice related financial transaction data generated by the one or more payee businesses as discussed in: U.S. patent application Ser. No. 15/140,117 (docket number INTU169676), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/140,131 (docket number INTU169677), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/142,708 (docket number INTU169678), filed on behalf of the same Inventors of the present patent application, filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein.
In one embodiment once access to invoice related financial transaction data generated by the one or more payee businesses is obtained at OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203, process flow proceeds to INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205.
In one embodiment, at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205, the invoice related financial transaction data of OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system.
In one embodiment, a personal financial management and bill payment system is provided using one or more computing systems.
In accordance with one embodiment, at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with the personal financial management and bill payment system using one or more processors associated with one or more computing systems.
In one embodiment, the personal financial management and bill payment system payment due data represents one or more payments due associated with one or more users of the personal financial management and bill payment system as payment due items to be paid through the personal financial management and bill payment system.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by assigning a personal financial management and bill payment system financial transaction category to the discrete invoices represented in the invoice related financial transaction data.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by providing the discrete invoices represented in the invoice related financial transaction data as line items in a payment due item listing generated through the personal financial management and bill payment system.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by assigning a personal financial management and bill payment system financial transaction category to the discrete invoices represented in the invoice related financial transaction data.
In accordance with one embodiment, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by any method, system, process and/or procedure for integrating invoice related financial transaction data into personal financial management and bill payment system payment due data as discussed herein, known in the art at the time of filing, and/or as developed/made available after the time of filing.
In accordance with various embodiments, the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by any method, system, process and/or procedure for integrating invoice related financial transaction data into personal financial management and bill payment system payment due data as discussed in: U.S. patent application Ser. No. 15/140,117 (docket number INTU169676), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/140,131 (docket number INTU169677), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein; and/or U.S. patent application Ser. No. 15/142,708 (docket number INTU169678), filed on behalf of the same Inventors of the present patent application, filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein.
In one embodiment, once the invoice related financial transaction data is integrated into personal financial management and bill payment system payment due data associated with a personal financial management and bill payment system at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205, process flow proceeds to RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207.
In one embodiment, at RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207, invoice payment request data is received from one or more users of the personal financial management and bill payment system.
As noted above, personal financial management and bill payment systems help a personal financial management and bill payment system user, or any authorized party acting on behalf of a personal financial management and bill payment system user, obtain financial transaction data representing financial transactions conducted by the user, process/analyze the financial transaction data, display categorized financial transaction data, generate financial transaction reports, generate bills due and payment due reports, and/or make manual, semi-automated, and/or automatic bill payments through the personal financial management and bill payment system.
As also noted above, some personal financial management and bill payment systems help users manage their finances and/or track their expenditures/financial transactions by providing a centralized interface with banks, credit card companies, and various other financial institutions, for electronically identifying and categorizing the user's financial transaction data. Currently, personal financial management and bill payment systems typically obtain electronic financial transaction data, such as payee data, payment amount data, transaction date data, etc. via communication with banks, credit card providers, or other financial institutions, using electronic data transfer systems, or various other systems for obtaining/transferring financial transaction data.
In addition, some personal financial management and bill payment systems include a payment due report/display generation feature. Typically, a payment due report includes personal financial management and bill payment system payment due data representing a listing of payments due, e.g., bill payment due items, within a defined period of time, such as a month, which require the user's attention.
As also noted above, in some cases, the users of the personal financial management and bill payment systems are also provided a bill payment service and the capability to make payments on a manual, semi-automatic, i.e., with user approval, or automatic, basis to various payees. In order to make these payments, the users of the personal financial management and bill payment systems typically enter data into the personal financial management and bill payment systems directing, or requesting, that one or more payments be made to one or more payees on a one-time, recurring, automatic, semi-automatic, or manual basis.
In the present embodiments, where invoice related financial transaction data has been integrated into the personal financial management and bill payment system payment due data at INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205, invoice payment requests are made by the users of the personal financial management and bill payment systems by entering, and/or providing, invoice payment request data.
In one embodiment, the invoice payment request data received by the personal financial management and bill payment system at RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207 represents one or more requests from one or more users of the personal financial management and bill payment system to pay one or more requested invoice payment amounts associated with one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data through the personal financial management and bill payment system.
In one embodiment, once invoice payment request data is received from one or more users of the personal financial management and bill payment system at RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207, process flow proceeds to OBTAIN ACCESS TO THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THE INTEGRATED INVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICE PAYMENT REQUEST DATA OPERATION 209.
In one embodiment, at OBTAIN ACCESS TO THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THE INTEGRATED INVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICE PAYMENT REQUEST DATA OPERATION 209, access to the personal financial management and bill payment system and the personal financial management and bill payment system payment due data, including the integrated invoice related financial transaction data, of INTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205, and the invoice payment request data of RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207 is obtained.
In accordance with one embodiment, one or more processors associated with one or more computing systems are utilized to obtain access to the personal financial management and bill payment system and the personal financial management and bill payment system payment due data, including the integrated invoice related financial transaction data, and the invoice payment request data at OBTAIN ACCESS TO THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THE INTEGRATED INVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICE PAYMENT REQUEST DATA OPERATION 209.
In one embodiment, once access to the personal financial management and bill payment system and the personal financial management and bill payment system payment due data, including the integrated invoice related financial transaction data, and the invoice payment request data is obtained at OBTAIN ACCESS TO THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THE INTEGRATED INVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICE PAYMENT REQUEST DATA OPERATION 209, process flow proceeds to ANALYZE THE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 211.
In one embodiment, at ANALYZE THE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 211, the invoice payment request data of RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207 is analyzed by to identify discrete invoice payment request related invoice data representing one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data.
In one embodiment, at ANALYZE THE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 211, the invoice payment request data is analyzed by one or more processors associated with one or more computing systems to identify discrete invoice payment request related invoice data representing one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data.
In one embodiment, once the invoice payment request data is analyzed to identify discrete invoice payment request related invoice data representing one or more discrete invoice payment request related invoices represented in the invoice related financial transaction data at ANALYZE THE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 211, process flow proceeds to IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213.
In one embodiment, at IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213, the integrated invoice related financial transaction data associated with the discrete invoice payment request related invoices of ANALYZE THE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 211 is analyzed to identify the payee business identity data associated with each discrete invoice payment request related invoice represented in the discrete invoice payment request related invoice data and a first payee business represented in the payee business identity data associated with two or more discrete first payee business invoice payment request related invoices represented in the discrete invoice payment request related invoice data is identified.
In one embodiment, at IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213, the integrated invoice related financial transaction data associated with the discrete invoice payment request related invoices is analyzed by one or more processors associated with one or more computing systems to identify the payee business identity data associated with each discrete invoice payment request related invoice represented in the discrete invoice payment request related invoice data and a first payee business represented in the payee business identity data associated with two or more discrete first payee business invoice payment request related invoices represented in the discrete invoice payment request related invoice data is identified.
In one embodiment, once a first payee business represented in the payee business identity data associated with two or more discrete first payee business invoice payment request related invoices represented in the discrete invoice payment request related invoice data is identified at IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213, process flow proceeds to AGGREGATE ALL THE INVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215.
In one embodiment, at AGGREGATE ALL THE INVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215, all the invoice related financial transaction data associated with the two or more discrete invoice payment request related invoices of IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213 is aggregated to generate aggregated first payee business invoice payment request invoice data.
In one embodiment, at AGGREGATE ALL THE INVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215, all the invoice related financial transaction data associated with the two or more discrete invoice payment request related invoices is aggregated by one or more processors associated with one or more computing systems to generate aggregated first payee business invoice payment request invoice data.
In one embodiment, once all the invoice related financial transaction data associated with the two or more discrete invoice payment request related invoices is aggregated to generate aggregated first payee business invoice payment request invoice data at AGGREGATE ALL THE INVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215, process flow proceeds to ANALYZE THE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217.
In one embodiment, at ANALYZE THE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217, the aggregated first payee business invoice payment request invoice data of AGGREGATE ALL THE INVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215 is analyzed to identify the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices.
In one embodiment, at ANALYZE THE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217, the aggregated first payee business invoice payment request invoice data is analyzed by one or more processors associated with one or more computing systems to identify the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices.
In one embodiment, once the aggregated first payee business invoice payment request invoice data is analyzed to identify the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices at ANALYZE THE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217, process flow proceeds to GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICE PAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 219.
In one embodiment, at GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICE PAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 219, the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices of ANALYZE THE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217 is processed and summed to generate aggregated total first payee business invoice payment amount data representing a total requested invoice payment amount for the first payee business as requested by two or more users of the personal financial management and bill payment system.
In one embodiment, at GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICE PAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 219, the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices is processed and summed by one or more processors associated with one or more computing systems to generate aggregated total first payee business invoice payment amount data representing a total requested invoice payment amount for the first payee business requested by two or more users of the personal financial management and bill payment system.
In one embodiment, once the requested invoice payment amount data associated with each of the two or more discrete invoice payment request related invoices is processed and summed to generate aggregated total first payee business invoice payment amount data representing a total requested invoice payment amount for the first payee business as requested by two or more users of the personal financial management and bill payment system at GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICE PAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 219, process flow proceeds to PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221.
In one embodiment, at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221, the aggregated total first payee business invoice payment amount data of GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICE PAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 219 is processed as a single first payee business funds transfer item using the personal financial management and bill payment system.
In one embodiment, at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221, the aggregated total first payee business invoice payment amount data is processed by one or more processors associated with one or more computing systems as a single first payee business funds transfer item using the personal financial management and bill payment system.
In accordance with one embodiment, processing the aggregated total first payee business invoice payment amount data as a single first payee business funds transfer item using the personal financial management and bill payment system at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 includes providing the aggregated total first payee business invoice payment amount data as a line item in a funds transfer item listing generated through the personal financial management and bill payment system.
In accordance with one embodiment, processing the aggregated total first payee business invoice payment amount data as a single first payee business funds transfer item using the personal financial management and bill payment system at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 includes applying one or more aggregated first payee business invoice payment request invoice data processing rules to the aggregated first payee business invoice payment request invoice data.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data processing rules of PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 include, but are not limited to, an aggregated first payee business invoice payment request invoice data processing rule limiting the aggregated total first payee business invoice payment amount to a threshold amount.
Using this aggregated first payee business invoice payment request invoice data processing rule, the financial risk associated with the single first payee business funds transfer transaction is limited to the threshold amount.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data processing rules of PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 include, but are not limited to, an aggregated first payee business invoice payment request invoice data processing rule limiting the total number of discrete invoices represented in the aggregated first payee business invoice payment request invoice data to a threshold number of discrete invoices.
Using this aggregated first payee business invoice payment request invoice data processing rule, the total liability associated with the single first payee business funds transfer transaction is limited to a total aggregated invoice amount associated with a threshold number of discrete invoices, thereby limiting the financial risk.
In accordance with one embodiment, the aggregated first payee business invoice payment request invoice data processing rules of PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 include any the aggregated first payee business invoice payment request invoice data processing rules desired, and/or as discussed herein, known in the art at the time of filing, and/or as developed/made available after the time of filing.
In one embodiment, once the aggregated total first payee business invoice payment amount data is then processed as a single first payee business funds transfer item using the personal financial management and bill payment system at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221, process flow proceeds to EXIT OPERATION 230.
In one embodiment, at EXIT OPERATION 230, process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is exited to await new data.
The disclosed embodiments of process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provide an efficient, effective, and highly adaptable solution to the long standing technical problem in the bill payment, invoice processing, and financial management arts of automatically integrating invoice related financial transaction data into a personal financial management and bill payment system, and/or identifying, or distinguishing, invoice related financial transaction data, and then aggregating requested invoice payment amounts associated with invoices represented in the invoice related financial transaction data having the same payee business into a single funds transfer transaction item to be processed by the personal financial management and bill payment system.
However, the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction does not encompass, embody, or preclude other forms of innovation in the area of automated financial transaction bill payment processing and invoicing. In addition, the process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is not related to any fundamental economic practice, fundamental data processing practice, mental steps, or pen and paper based solution. In fact, the disclosed embodiments are directed to providing solutions to the relatively new problems associated with the automatic processing and display of electronic financial transaction data obtained from multiple sources, making electronic bill payments, and the management and processing of large amounts of data, i.e., “big data.” Consequently, the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction is not directed to, does not encompass, and is not merely, an abstract idea or concept.
In addition, the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for significant improvements to the technical fields of electronic transaction data processing, invoicing, financial transaction categorization, information dissemination, data processing, data management, data filtering and mining, automatic electronic bill payment, and user experience.
In addition, by allowing for the integration of invoices and invoice data into a personal financial management and bill payment system, the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction helps users of the personal financial management and bill payment system identify and pay their invoices. This, in turn, helps avoid the reissuance and repeated transmission of payment due reminders and for the entry, processing, and dissemination, of redundant invoice data; thereby eliminating unnecessary data analysis before resources are allocated to processing, and/or correcting, redundant reminder data and the redundant reminder data is further transmitted/distributed.
Consequently, using the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction results in more efficient use of human and non-human resources, fewer processor cycles being utilized, reduced memory utilization, and less communications bandwidth being utilized to relay data to, and from, backend systems and client systems.
As a result, computing systems are transformed into faster, more efficient, and more effective computing systems by implementing process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction.
In addition, the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for the entry, processing, and dissemination, of only relevant portions of data; thereby eliminating unnecessary data analysis and correction before resources are allocated to processing, and/or correcting, faulty/irrelevant data, and/or the faulty/irrelevant data is further transmitted/distributed.
In addition, by aggregating requested invoice payment amounts associated with multiple invoices represented in the invoice related financial transaction data having the same payee business into single funds transfer item, the disclosed process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction provides for the processing and dissemination of invoice related financial transaction data representing multiple discrete invoices as a single funds transfer entity/object. This, in turn, helps avoid the processing and transmission of multiple individual invoice payment related data sets and related funds transfer transaction data sets.
Consequently, using process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction results in more efficient use of human and non-human resources, fewer processor cycles being utilized, reduced memory utilization, and less communications bandwidth being utilized to relay data to, and from, backend systems and client systems.
As a result, computing systems are transformed into faster, more efficient, and more effective computing systems by implementing process 200 for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single funds transfer transaction.
The present invention has been described in particular detail with respect to specific possible embodiments. Those of skill in the art will appreciate that the invention may be practiced in other embodiments. For example, the nomenclature used for components, capitalization of component designations and terms, the attributes, data structures, or any other programming or structural aspect is not significant, mandatory, or limiting, and the mechanisms that implement the invention or its features can have various different names, formats, and/or protocols. Further, the system and/or functionality of the invention may be implemented via various combinations of software and hardware, as described, or entirely in hardware elements. Also, particular divisions of functionality between the various components described herein, are merely exemplary, and not mandatory or significant. Consequently, functions performed by a single component may, in other embodiments, be performed by multiple components, and functions performed by multiple components may, in other embodiments, be performed by a single component.
Some portions of the above description present the features of the present invention in terms of algorithms and symbolic representations of operations, or algorithm-like representations, of operations on information/data. These algorithmic and/or algorithm-like descriptions and representations are the mechanism and/or process used by those of skill in the art to most effectively and efficiently convey the substance of their work to others of skill in the art. These operations, while described functionally or logically, are understood to be implemented by computer programs and/or computing systems. Furthermore, it has also proven convenient at times to refer to these arrangements of operations as steps or modules or by functional names, without loss of generality.
Unless specifically stated otherwise, as would be apparent from the above discussion, it is appreciated that throughout the above description, discussions utilizing terms such as “integrating,” “generating,” “monitoring,” “determining,” “defining,” “designating,” “obtaining,” “accessing,” “analyzing,” “obtaining,” “identifying,” “designating,” categorizing,” “receiving,” “transmitting,” “implementing,” “associating,” “aggregating,” “initiating,” “collecting,” “creating,” “transferring,” “storing,” “searching,” “comparing,” “providing,” “transforming,” “incorporating.” “processing” etc., refer to the action and processes of a computing system or similar electronic device that manipulates and operates on data represented as physical (electronic) quantities within the computing system memories, resisters, caches or other information storage, transmission or display devices.
Certain aspects of the present invention include process steps or operations and instructions described herein in an algorithmic and/or algorithmic-like form. It should be noted that the process steps and/or operations and instructions of the present invention can be embodied in software, firmware, and/or hardware, and when embodied in software, can be downloaded to reside on and be operated from different platforms used by real time network operating systems.
The present invention also relates to an apparatus or system for performing the operations described herein. This apparatus or system may be specifically constructed for the required purposes by a computer program stored via a computer program product as defined herein that can be accessed by a computing system or other device to transform the computing system or other device into a specifically and specially programmed computing system or other device.
Those of skill in the art will readily recognize that the algorithms and operations presented herein are not inherently related to any particular computing system, computer architecture, computer or industry standard, or any other specific apparatus. It may prove convenient/efficient to construct or transform one or more specialized apparatuses to perform the required operations described herein. The required structure for a variety of these systems will be apparent to those of skill in the art, along with equivalent variations. In addition, the present invention is not described with reference to any particular programming language and it is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references to a specific language or languages are provided for illustrative purposes only and for enablement of the contemplated best mode of the invention at the time of filing.
The present invention is well suited to a wide variety of computer network systems operating over numerous topologies. Within this field, the configuration and management of large networks comprise storage devices and computers that are communicatively coupled to similar and/or dissimilar computers and storage devices over a private network, a LAN, a WAN, a private network, or a public network, such as the Internet.
It should also be noted that the language used in the specification has been principally selected for readability, clarity, and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the claims below.
In addition, the operations shown in the FIG.s are identified using a particular nomenclature for ease of description and understanding, but other nomenclature is often used in the art to identify equivalent operations.
In the discussion above, certain aspects of one embodiment include process steps and/or operations and/or instructions described herein for illustrative purposes in a particular order and/or grouping. However, the particular order and/or grouping shown and discussed herein is illustrative only and not limiting. Those of skill in the art will recognize that other orders and/or grouping of the process steps and/or operations and/or instructions are possible and, in some embodiments, one or more of the process steps and/or operations and/or instructions discussed above can be combined and/or deleted. In addition, portions of one or more of the process steps and/or operations and/or instructions can be re-grouped as portions of one or more other of the process steps and/or operations and/or instructions discussed herein. Consequently, the particular order and/or grouping of the process steps and/or operations and/or instructions discussed herein does not limit the scope of the invention as claimed below.
Therefore, numerous variations, whether explicitly provided for by the specification or implied by the specification or not, may be implemented by one of skill in the art in view of this disclosure.
This application is related to U.S. patent application Ser. No. 15/140,117 (docket number INTU169676), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein. This application is also related to U.S. patent application Ser. No. 15/140,131 (docket number INTU169677), filed on behalf of the same Inventors of the present patent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein. This application is also related to U.S. patent application Ser. No. 15/142,708 (docket number INTU169678), filed on behalf of the same Inventors of the present patent application, filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated by reference in its entirety as if it were fully set forth herein.
