Abstract: A computer system for modelling transactions is provided that includes a processor a data store coupled to the processor. The data store containing a plurality of cost object models and a plurality of cost elements. The processor is configured to receive an indication of a cost event and flow an aspect of the cost event through at least one cost object stored in the data store.

Abstract: Technologies are generally described for a system enabling modeling of a dimensional multi-level scale for data management. A transactional data system may be configured to track data for a variety organizations and to generate a dimensional multi-level scale for data tracked by the transactional data system based on a combination of attributes and values for each data measure tracked and recorded. The dimensional multi-level scale may define a collection of hierarchical units, where a unit may represent a tracked piece of data and may include multiple levels and sub-levels. Each unit may be characterized by attributes and attribute values at a given level in the hierarchy such that the combination of attributes and values may identify the unit. Additionally, each unit may enable additional attributes and values to be defined to further characterize a sub-level of the unit, where each sub-level may provide additional data about the unit.

Abstract: Technologies are generally described to leverage a multidimensional measurement basis for cost accounting in a cost accounting system to increase cohesion of the system. One or more scales for units of measure may be defined based on a magnitude of product cost and a product cost measure determined by various subsystems of the cost accounting system. The magnitude of product cost may be determined based on a cost object unit, a cost element unit, a date and time unit, and a quantity unit, and the product cost measure may be determined based on a cost base and a unit cost. The scales defined may be applied to cost accounting in a reporting ledger of the cost accounting system and a report may be generated from the reporting ledger that enables cost analysis based on the scales defined.

Abstract: Technologies are generally described for accounting for contract formation and fulfillment activities by combination event chaining and multidimensional measurement chaining, with event and measurement matching rules that apply variance and tolerance policies during evaluation. Building on chaining basis and derived measurements that participate in an equality relationship, chaining measurements may participate in a matching rule that applies tolerance policies. Furthermore, measurement chaining may be updated when the documented consequence of events are corrected or changed.

Abstract: Technologies are generally described for a consistent process, task, and state application architecture pattern from an initial documentation process through the resource accounting, subledger accounting processes, and the general ledger accounting process. Data driven policy and rules may be leveraged for the processing to determine input, results, and state transitioning, where processes may represent operations performed by the accounting system. The application process pattern may be an abstraction of key domain processes and their generic tasks and states. The framework tasks may leverage explicit policy and rule types and/or procedures to determine a result and to validate the state transition.

Abstract: Techniques to provide a multi-measurement basis for accounting systems are described. A technique may include receiving data from a source document, documenting the received data as base multidimensional measurements that characterize an event, calculating derived multidimensional measurements that quantify the social, operational, and financial consequences of the event from the base multidimensional measurements. Derived measurements are linked to base measurements in measurement chains. Events that are related causally may be linked together in event chains. The measurement chains and event chains may be used to generate subledger journal entries, which may in turn be used to generate general ledger journal entries. An event may capture information about an event beyond what may be reflected in the source document. Other embodiments are described and claimed.

Abstract: A method and an apparatus for generating reports and other outputs from a computer program. A user first defines a focus area, composed of chosen data types and then creates a row definition for the focus area. In defining the row definition the user defines groups and subgroups from the data represented by the focus. This definition process allows the user to generate reports from data organized in similar rows. The user has the ability to define the data to be included in the report through the use of an expression. The expression can also be used to exclude data from the report. Additional embodiments allow the user to verify the use of data and if the data has been used multiple times, and to capture on the output the missings and duplicates.

Abstract: A computer-implemented accounting system supports financial transaction data entry using dimensions. Dimension sets are defined to include one or more selected dimensions. A hierarchy is defined relative to a dimension set, which hierarchy constrains allowed dimension values relative to the dimension set. One or more rules are defined relative to the hierarchy to further constrain dimension values or combinations of values. A method of configuring a computer-implemented accounting system is provided. A method of entering data into a computer-implemented accounting system is also provided.

Abstract: A method and an apparatus for generating reports and other outputs from a computer program. A user first defines a focus area, composed of chosen data types and then creates a row definition for the focus area. In defining the row definition the user defines groups and subgroups from the data represented by the focus. This definition process allows the user to generate reports from data organized in similar rows. The user has the ability to define the data to be included in the report through the use of an expression. The expression can also be used to exclude data from the report. Additional embodiments allow the user to verify the use of data and if the data has been used multiple times, and to capture on the output the missings and duplicates.