1. A system for centralized collaborative licensee-owner information account computer management of data, wherein the data is input into specific licensee-user data sources which is not necessarily employing a remote information computer access, comprising; central digital data storage and processing components which includes at least one remote access device interface component; remote user access transmitting discrete units of user specific work-product data and data output requests; associating said user specific work-product data with one to a plurality of user process ledger modules (UPLM), wherein the associating comprises; a selection of one to a plurality of UPLMs implemented as discreet units to accomplish specific application tasks, and user specific data input options which are placed into an intermediate processing for further specific user process programming, hereafter the intermediate processing will be referred to as a licensee-owner configuration template (UPLM CT), and then into final processing components, wherein the tasks being implemented by the one to a plurality of UPLMs, the tasks including: implementing operating system type components, the components including: a data entry point member, an entry location of data, an association of components, a destination directory, a data server application procedures, implementing installed application services, the application services including: a central application component, a central data management application component, a interface application service, a interface device service, user selected references for selected applications including required support components needed for said selections, a retrieval application, a requirement for proper application processing, background information in areas of expertise of said UPLMs, background information in areas of expertise of remotely access application, a licensee-owner database structure, a database access application, a remote access information application, a user specific remote access application, implementing data store type components, the data store type components including: data storage in a relational database, data storage in a non-relational database, data storage in an ASCII text file having delimited or fixed length fields, data downloaded into a text file from a network, data storage from a network by internet, main frame, local, or single computer data search, and retrieval, implementing text file components, the text file components including: a data file conversion component from an unsupported data management application or operating system, an ad hoc data file generation component with a text editor, a text file input or output operation component including a log file component, a data reading component for reading data from said selected data files, updating fields, adding new records, a data writing component for writing data back to text file for output generation, implementing database components, the database components including: a manage data binding component, adding and saving data to an underlying database, as a new record from a said UPLM specific data sets, an enabling data entry for record update, a rolling back at least one of said UPLM specific data sets or associated database on occurrence of associated process or system error events or decision to cancel process, a licensee-owner account database storage space selection, a database for items selected in separate application, one to a multiple specific information retrieval about data type retrieved from a database connection, implementing plug-in components, the plug-in components including: ActiveX controls, Java applets, any plug in technology, and wherein the user specific data input options and the units of central data management components are selected and implemented as discreet units creating said UPLM CTs, wherein the UPLM CTs are generated by a localization tool, the generation of the UPM CTs includes: binding data in a grouping hierarchy data set to a set of controls on a form, binding data in a relation hierarchy data set to a set of controls on a form, configuring a collection of file templates that export reports in at least one of a plurality of data formats, and passing data from an application or object to another application or object, wherein the UPLM CT is at least on of a plurality of layouts containing objects, wherein the localization tool: tracks any additions, changes, or deletions of UPLMs, accesses selection of directories of native language voice filed which are used for UPLM implementation, stores alert and error messages containing replacement parameters of text and character sets; and connecting said remote access device interface component to said associating said user specific work-product data with one to a plurality of UPLMs, wherein each UPLM: is not limited to a visual display, and selection requests are limited to the user and are based on the licensee-user data structure by predetermined UPLM configured options, where all selections are generated by input selections that are specific only to each user.