Abstract: Funding source data, such as bank account information or credit card information, associated with a user is stored in an enterprise-wide database maintained by an institution, such as a financial services institution. The data in the enterprise-wide database may be accessible to entities associated with the institution upon the user's authorization. The user only has to provide the funding source data once and may then use that funding source to pay for any product, service, bill, etc. associated with any of the entities of the institution. A user may update funding source data once, and this updated funding source data may then be available to all the entities. After providing account details for the user's various funding sources, a user can assign any of the funding sources to a payment plan for any product or service in any entity of the institution.

Abstract: Systems and methods for directing the transfer of funds are described. Funds to be distributed to a user are received by the system. User distribution preferences are read and the funds are distributed to various sources according to the preferences. Other embodiments are also described and claimed.

Abstract: A method of managing all personal financial accounts is accomplished by providing an electronically accessible repository containing financial asset and liability account information. The repository may be electronically accessed by various access channels for reviewing the status of any account in the repository, transferring an external account into the repository, creating a new account in the repository, transferring account adjustments into and out of the repository, making account adjustments within the repository, closing or deleting an account within the repository, presenting a bill to the repository, and paying a bill from one or more accounts in the repository.

Abstract: A recurring automatic payment date may be set for an insurance policy premium based on customer preference. A server may receive a customer-specified day of a month and/or a request for bimonthly withdrawals, such as may be entered via a user interface on an insurance company webpage. The customer specified day(s) may be analyzed against data associated with the insurance policies to determine whether the day is disallowed. The day may be disallowed, for example, because it would result in falling behind an earned premium curve and thereby require a double bill or short bill to stay ahead of the earned premium curve.

Abstract: A user may log into a system containing data pertaining to a jointly owned funding account of which he is a co-owner. The user may view information directed to the jointly owned funding account, such as his bills and bills associated with other co-owners. The user may pay bills or schedule payments of bills from the funding account. A co-owner of the funding account may set up an account with a biller and enable other co-owners of the funding account to use this information, thereby providing the other co-owners with the same or similar functionality when they log into the system using their own login information. The information that the co-owner may set up with a biller may be ported over to the information maintained by the system that is directed to the other co-owners.

Abstract: Funding source data, such as bank account information or credit card information, associated with a user is stored in an enterprise-wide database maintained by an institution, such as a financial services institution. The data in the enterprise-wide database may be accessible to entities associated with the institution upon the user's authorization. The user only has to provide the funding source data once and may then use that funding source to pay for any product, service, bill, etc. associated with any of the entities of the institution. A user may update funding source data once, and this updated funding source data may then be available to all the entities. After providing account details for the user's various funding sources, a user can assign any of the funding sources to a payment plan for any product or service in any entity of the institution.

Abstract: A method of managing all personal financial accounts is accomplished by providing an electronically accessible repository containing financial asset and liability account information. The repository may be electronically accessed by various access channels for reviewing the status of any account in the repository, transferring an external account into the repository, creating a new account in the repository, transferring account adjustments into and out of the repository, making account adjustments within the repository, closing or deleting an account within the repository, presenting a bill to the repository, and paying a bill from one or more accounts in the repository.

Abstract: A recurring automatic payment date may be set for an insurance policy premium based on customer preference. A server may receive a customer-specified day of a month and/or a request for bimonthly withdrawals, such as may be entered via a user interface on an insurance company webpage. The customer specified day(s) may be analyzed against data associated with the insurance policies to determine whether the day is disallowed. The day may be disallowed, for example, because it would result in falling behind an earned premium curve and thereby require a double bill or short bill to stay ahead of the earned premium curve.

Abstract: A user may log into a system containing data pertaining to a jointly owned funding account of which he is a co-owner. The user may view information directed to the jointly owned funding account, such as his bills and bills associated with other co-owners. The user may pay bills or schedule payments of bills from the funding account. A co-owner of the funding account may set up an account with a biller and enable other co-owners of the funding account to use this information, thereby providing the other co-owners with the same or similar functionality when they log into the system using their own login information. The information that the co-owner may set up with a biller may be ported over to the information maintained by the system that is directed to the other co-owners.

Abstract: A recurring automatic payment date may be set for an insurance policy premium based on customer preference. A server may receive a customer-specified day of a month and/or a request for bimonthly withdrawals, such as may be entered via a user interface on an insurance company webpage. The customer specified day(s) may be analyzed against data associated with the insurance policies to determine whether the day is disallowed. The day may be disallowed, for example, because it would result in falling behind an earned premium curve and thereby require a double bill or short bill to stay ahead of the earned premium curve.

Abstract: A recurring automatic payment date may be set for an insurance policy premium based on customer preference. A server may receive a customer-specified day of a month and/or a request for bimonthly withdrawals, such as may be entered via a user interface on an insurance company webpage. The customer specified day(s) may be analyzed against data associated with the insurance policies to determine whether the day is disallowed. The day may be disallowed, for example, because it would result in falling behind an earned premium curve and thereby require a double bill or short bill to stay ahead of the earned premium curve.

Abstract: A recurring automatic payment date may be set for an insurance policy premium based on customer preference. A server may receive a customer-specified day of a month and/or a request for bimonthly withdrawals, such as may be entered via a user interface on an insurance company webpage. The customer specified day(s) may be analyzed against data associated with the insurance policies to determine whether the day is disallowed. The day may be disallowed, for example, because it would result in falling behind an earned premium curve and thereby require a double bill or short bill to stay ahead of the earned premium curve.

Abstract: Systems and methods for providing dynamic integration and access to disparate data sources are described. The apparatus may include an internal data source access engine, an external data source access engine, an integration engine and a user interface module. The method may comprise receiving a request for bill-pay services from a user, first retrieving internal bill-pay information, second retrieving external bill-pay information, integrating the first retrieved and second retrieved information into a single unified graphical presentation, presenting the unified graphical presentation to the user.

Abstract: A method of managing all personal financial accounts is accomplished by providing an electronically accessible repository containing financial asset and liability account information. The repository may be electronically accessed by various access channels for reviewing the status of any account in the repository, transferring an external account into the repository, creating a new account in the repository, transferring account adjustments into and out of the repository, making account adjustments within the repository, closing or deleting an account within the repository, presenting a bill to the repository, and paying a bill from one or more accounts in the repository.