Abstract: In one embodiment, the present invention is a method of sending change information from a first database to a second database. The method includes managing a set of transactions to produce a first message. The method also includes transforming the first message into a second message. The method further includes converting the second message into a transmittable message. In an alternate embodiment, the present invention is a method of receiving change information for a second database from a first database. The method includes converting a received message into a second message. The method further includes transforming the second message into a third message. The method also includes processing the third message to form a set of transactions. The method may further include effecting changes in the second database with the set of transactions.

Abstract: In one embodiment, the present invention is a method of sending change information from a first database to a second database. The method includes managing a set of transactions to produce a first message using custom scripts and default processing. The method also includes transforming the first message into a second message using custom scripts and default processing. The method further includes converting the second message into a transmittable message using custom scripts and default processing. In an alternate embodiment, the present invention is a method of receiving change information for a second database from a first database. The method includes converting a received message into a second message using custom scripts and default processing. The method further includes transforming the second message into a third message using custom scripts and default processing. The method also includes processing the third message to form a set of transactions using custom scripts and default processing.

Abstract: A data model that allows for relationships between entities, also referred to as parties, to be modeled as attributes of an entity and for customization of the data model in a manner that facilitates upgrading of the data model. In some embodiments, the data model may facilitate creation and processing of financial applications. Using the data model, received application data can be stored in a financial application record, including data relating to a party's financial statements. In some embodiments, the data model may facilitate management of financial account data for multiple accounts. In some embodiments the data model may facilitate management of credit information, such as credit information collected by credit bureaus.

Abstract: In one embodiment, the present invention is a method of dispatching information within a system. The method includes receiving a message. The method also includes extracting address information from the message. The method further includes determining a destination from the address information. The method also includes routing the message to the destination.

Abstract: In one embodiment, the present invention is a method of sending change information from a first database to a second database. The method includes managing a set of transactions to produce a first message. The method also includes transforming the first message into a second message. The method further includes converting the second message into a transmittable message.

Abstract: Data objects can be cross-referenced or linked between multiple systems by normalizing the communications between the multiple systems rather than creating hard code links. The normalization includes creating and inserting data mapping information in messages exchanged by the multiple systems, according to certain embodiments. According to certain other embodiments, an alert mechanism may be included in the message to indicate that mapping information is present in the message.

Abstract: A system and method for the management of information in an enterprise system are disclosed. In one embodiment, the enterprise system includes a primary system and a legacy system. The primary system includes an application or interface that can be used to communicate with and receive communications from a legacy system. In another embodiment, a legacy system can include an application or interface that can be used to communicate with and receive communications from the primary system. The primary system includes a database with information for the enterprise system. In one embodiment, the primary system provides updates to the legacy system of any changes in the information in the database. In another embodiment, a legacy system can select updates to particular enterprise information that it wants to receive from the primary system.

Abstract: A system and method for enabling the cross-referencing or linking of records in an enterprise system is disclosed.