Abstract: Aspects of the present disclosure provide techniques for rule-based document security. Embodiments include receiving, from a computing device: an amended document; an encrypted sensitive component; and information relating to reconstructing a document based on the amended document and the encrypted sensitive component. Embodiments include decrypting the encrypted sensitive component to produce a decrypted sensitive component. Embodiments include determining, based on the information relating to reconstructing the document, a document location that corresponds to the decrypted sensitive component. Embodiments include reconstructing the document by inserting the decrypted sensitive component into the amended document at the document location.

Abstract: Financial transaction data is obtained and integrated into a personal financial management and bill payment system. Payment method data associated with the financial transaction data is obtained from the personal financial management and bill payment system. The payment method data is then used to more accurately and automatically identify tax related financial transactions for processing as tax related financial transactions having tax ramifications.

Abstract: Financial transaction data is obtained and integrated into a personal financial management and bill payment system. Payment method data associated with the financial transaction data is obtained from the personal financial management and bill payment system. The payment method data is then used to more accurately and automatically identify tax related financial transactions for processing as tax related financial transactions having tax ramifications.

Abstract: Invoice related financial transaction data is obtained and integrated into a personal financial management and bill payment system. All invoices represented in the invoice related financial transaction data having the same payor user of the personal financial management and bill payment system and the same payee business are then identified and collected into aggregated same payor/same payee invoice related financial transaction data. The aggregated same payor/same payee invoice related financial transaction data is then analyzed to determine the aggregated total amount owed to the payee business by the payor user and this aggregated total amount is processed as a single payment due item by the personal financial management and bill payment system.

Abstract: 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 collected into aggregated first payee business invoice payment request related financial transaction data. The aggregated first payee business invoice payment request related financial transaction data is then analyzed to determine the aggregated total amount owed to the payee business and this aggregated total amount is processed as a single funds transfer item by the personal financial management and bill payment system.

Abstract: Invoice related financial transaction data is obtained and integrated into a personal financial management and bill payment system. The integrated invoice related financial transaction data is then analyzed to identify and extract additional invoice related financial transaction data, such as Level-3 financial transaction data, included in the invoice related financial transaction data. The additional invoice related financial transaction data is then used to more accurately and automatically identify tax related financial transactions for processing as tax related financial transactions having tax ramifications.

Abstract: Invoice related financial transaction data is obtained and integrated into a personal financial management and bill payment system. All invoices represented in the invoice related financial transaction data having the same payor user of the personal financial management and bill payment system and the same payee business are then identified and collected into aggregated same payor/same payee invoice related financial transaction data. The aggregated same payor/same payee invoice related financial transaction data is then analyzed to determine the aggregated total amount owed to the payee business by the payor user and this aggregated total amount is processed as a single payment due item by the personal financial management and bill payment system.

Abstract: Personal financial management and bill payment system user identification data associated with users of a personal financial management and bill payment system and business invoicing system customer identification data associated with customers of user businesses of a business invoicing system is obtained and analyzed to identify users of the personal financial management and bill payment system that are customers of business users of the business invoicing system. Once a user of the personal financial management and bill payment system that is also a customer of a business user of the business invoicing system is identified, the business user of the business invoicing system is provided the capability to provide invoice data representing invoices generated by the business user of the business invoicing system to the user of the personal financial management and bill payment system through the personal financial management and bill payment system.

Abstract: When an invoice is generated by a business through a business invoicing system, the invoice data is obtained and analyzed to identify customer identification data associated with, and identifying, the customer of the business to whom the invoice is directed. The customer identification data is then used to search user identification data associated with users of a personal financial management and bill payment system to determine if the customer of the business is also a user of the personal financial management and bill payment system. If it is determined that the customer of the business is also a user of the personal financial management and bill payment system, the business is provided the capability and opportunity to provide invoicing data representing invoices generated by the business through the business invoicing system to the customer through the personal financial management and bill payment system used by the customer.

Abstract: Financial transaction data representing financial transactions associated with a user of a personal financial management and bill payment system is obtained from, or through, the personal financial management and bill payment system. The financial transaction data is then analyzed to identify payee data representing the payees of financial transactions. The payee data is then compared with business user identification data representing users of a business invoicing system. If a match is found between a payee represented in the payee data and a business user represented in the business invoicing system, the associated payment is identified and processed as an invoice payment and the business user of the business invoicing system is provided the capability to provide invoicing data representing invoices generated by the business user to the user of the personal financial management and bill payment system through the personal financial management and bill payment system.

Abstract: The disclosed embodiments provide a system that ensures the integrity of a downloaded data set. During operation, a browser application executing on a computing device receives a data set that was signed using the private key of a host computer. The browser application stores this signed data set in a browser data store. Subsequently, the browser application also receives a public key from the host computer (e.g., while accessing a web page associated with the signed data set). The browser application ensures the integrity of the data set by executing scripted program code that: uses the public key to decode the signature for the data set; calculates a hash value for the signed data set; and compares the decoded signature with the hash value to validate the data set.

Abstract: An object-oriented file system in an object-oriented operating system includes a file system entity class that is subclassed into a volume, directory and file subclass. These classes encapsulate standard file system properties such as name, creation date, and size, as well as standard operations such as create, open, close, and property accessors. Using object-oriented programming, the class properties and operations can easily be modified and extended. Also provided is a convenient and efficient means for searching through the entities, and collecting heterogeneous sets. Further, a category of notification classes is provided for notifying clients when an entity has changed. Still further, user authentication and protection domains are used to protect against unauthorized access. Finally, a means for working with foreign file systems running under different operating systems is provided.

Abstract: An object-oriented file system in an object-oriented operating system includes a file system entity class that is subclassed into a volume, directory and file subclass. These classes encapsulate standard file system properties such as name, creation date, and size, as well as standard operations such as create, open, close, and property accessors. Using object-oriented programming, the class properties and operations can easily be modified and extended. Also provided is a convenient and efficient means for searching through the entities, and collecting heterogeneous sets. Further, a category of notification classes is provided for notifying clients when an entity has changed. Still further, user authentication and protection domains are used to protect against unauthorized access. Finally, a means for working with foreign file systems running under different operating systems is provided.