Abstract: A method of accelerating transactions for a relational database using a pre-populated multidimensional data cube includes pre-populating the multidimensional data cube based on values from the relational database system; executing one or more transactions using values in the multidimensional data cube instead of using the values from the relational database system; generating one or more entries that update the relational database system using results generated from executing the one or more transactions; posting the one or more entries to the relational database system; and repopulating the multidimensional data cube based on values from the relational database system that changed as a result of posting the one or more entries to the relational database system.

Abstract: A method of accelerating transactions for a relational database using a pre-populated multidimensional data cube includes pre-populating the multidimensional data cube based on values from the relational database system; executing one or more transactions using values in the multidimensional data cube instead of using the values from the relational database system; generating one or more entries that update the relational database system using results generated from executing the one or more transactions; posting the one or more entries to the relational database system; and repopulating the multidimensional data cube based on values from the relational database system that changed as a result of posting the one or more entries to the relational database system.

Abstract: A method of accelerating execution of a transactions includes storing financial ledgers in a relational database, prepopulating a multidimensional data cube using the relational database, executing the transactions using the data cube by querying the data cube for aggregated balances to generate result values, generating accounting journal entries that update each account in the ledgers affected by the transactions using the result values from the data cube, posting the accounting journal entries to the financial ledgers in the relational database, repopulating the data cube with the changes resulting from the posted journal entries, and updating the aggregated balances of the data cube.

Abstract: In an embodiment, for any structural change that is made to a relational database, a corresponding change is also made to the multidimensional database. In an embodiment, the system determines that a particular structure is not implemented on the multidimensional database system. Based on metadata that defines the structure that is supposed to exist in the multidimensional database, the appropriate structure is created.

Abstract: In an embodiment, for any structural change that is made to a relational database, a corresponding change is also made to the multidimensional database. In an embodiment, the system determines that a particular structure is not implemented on the multidimensional database system. Based on metadata that defines the structure that is supposed to exist in the multidimensional database, the appropriate structure is created.

Abstract: Systems, methods, and computer-readable media for acceleration of system documentation conformance to differentiated regulations of multiple countries are provided. A database may be prepopulated with documentation specifications specifying documentation attributes corresponding to transaction types and countries. Information indicative of an enterprise structure may be processed. Countries that correspond to the enterprise structure may be identified. Country-specific rules may be determined, the rules defining requirements pertaining to documentation of transactions. A first subset of documentation attributes may be selected based on the rules, the first subset specifying documentation options pertaining to a first transaction type. A second subset of documentation attributes may be selected based on the rules, the second subset specifying documentation options pertaining to a second transaction type. A set of objects to facilitate setup of an accounting program may be generated.

Abstract: A method of detecting variances in a plurality of accounts from different organizations within an Enterprise Financial Accounting system includes receiving a selection of a first account with an account type; receiving a selection of a first time interval and a second time interval; determining a first amount that is associated with the first account during the first time interval; determining a second amount that is associated with the first account during the second time interval; receiving a selection of a comparison operator that relates the first amount to the second amount; receiving a selection of a threshold; determining a comparison value by comparing the first amount to the second amount according to the comparison operator; determining that the comparison value violates the threshold according to the comparison operator; and displaying a first indication in a portal comprised of the first amount, the second amount, and the comparison value.

Abstract: Systems, methods, and computer-readable media for acceleration of system documentation conformance to differentiated regulations of multiple countries are provided. A database may be prepopulated with documentation specifications specifying documentation attributes corresponding to transaction types and countries. Information indicative of an enterprise structure may be processed. Countries that correspond to the enterprise structure may be identified. Country-specific rules may be determined, the rules defining requirements pertaining to documentation of transactions. A first subset of documentation attributes may be selected based on the rules, the first subset specifying documentation options pertaining to a first transaction type. A second subset of documentation attributes may be selected based on the rules, the second subset specifying documentation options pertaining to a second transaction type. A set of objects to facilitate setup of an accounting program may be generated.

Abstract: Setup of accounts in accounting software is automated, based on user input on (1) a name of an account of a specific type, and (2) a specific value to be used to identify the account uniquely, among other accounts of the specific type. The account's name is used by one or more computers to automatically look up N unique values that identify N entities of an organization. Then, a pattern of segments that defines an account identifier is automatically used by the one or more computers, to insert into the pattern the specific value and each of the N unique values, to obtain N account identifiers. Thereafter, N tuples are automatically formed by the one or more computers and stored in a table, each tuple comprising one of the N account identifiers, and the account's name. Subsequently, N accounts are setup in the accounting program, based on the N tuples.

Abstract: In an embodiment, for any structural change that is made to a relational database, a corresponding change is also made to the multidimensional database. In an embodiment, the system determines that a particular structure is not implemented on the multidimensional database system. Based on metadata that defines the structure that is supposed to exist in the multidimensional database, the appropriate structure is created.

Abstract: In an embodiment, for any structural change that is made to a relational database, a corresponding change is also made to the multidimensional database. In an embodiment, the system determines that a particular structure is not implemented on the multidimensional database system. Based on metadata that defines the structure that is supposed to exist in the multidimensional database, the appropriate structure is created.

Abstract: A method of accelerating execution of a transactions includes storing financial ledgers in a relational database, prepopulating a multidimensional data cube using the relational database, executing the transactions using the data cube by querying the data cube for aggregated balances to generate result values, generating accounting journal entries that update each account in the ledgers affected by the transactions using the result values from the data cube, posting the accounting journal entries to the financial ledgers in the relational database, repopulating the data cube with the changes resulting from the posted journal entries, and updating the aggregated balances of the data cube.

Abstract: A method of using rules to execute periodic allocations of funds in a hierarchal accounting structure may include receiving an allocation rule, comprising a source account, a rule for determining a first amount, a parent account, and an allocation basis; accessing a multidimensional data cube comprising a hierarchal arrangement and aggregated balances for each level of the hierarchal arrangement; generating an allocation scenario by allocating the first amount to the aggregated balances for the one or more child accounts according to the allocation rule; generating one or more accounting journal entries corresponding to the allocation scenario; posting the one or more accounting journal entries to a general ledger associated with a relational database; and updating, using the relational database, the multidimensional data cube to reflect the allocation scenario.

Abstract: A method of using a formula to execute periodic transfers in a hierarchal accounting structure includes receiving a transfer formula that may comprise a source account, a target account, an offset account, an account characteristic, and a formula for determining a first amount of the source account based on the account characteristic. The method may also include accessing a multidimensional data cube with a hierarchal arrangement and aggregated balances for each level. The method may additionally include generating a transfer scenario by transferring the first amount to the aggregated balance for the target account according to the transfer formula, and generating one or more accounting journal entries corresponding to the transfer scenario. The method may further include posting the one or more accounting journal entries to a general ledger associated with a relational database; and updating the multidimensional data cube to reflect the transfer scenario.

Abstract: A method of using a formula to execute periodic transfers in a hierarchal accounting structure includes receiving a transfer formula that may comprise a source account, a target account, an offset account, an account characteristic, and a formula for determining a first amount of the source account based on the account characteristic. The method may also include accessing a multidimensional data cube with a hierarchal arrangement and aggregated balances for each level. The method may additionally include generating a transfer scenario by transferring the first amount to the aggregated balance for the target account according to the transfer formula, and generating one or more accounting journal entries corresponding to the transfer scenario. The method may further include posting the one or more accounting journal entries to a general ledger associated with a relational database; and updating the multidimensional data cube to reflect the transfer scenario.

Abstract: Various arrangements for posting a journal entry to a ledger are presented. The journal entry that comprises financial information related to a credit or debit from an account may be received. A request to post the journal entry to the ledger may be received. The journal entry may be determined to be subject to an approval process at least based on the ledger. At least one entity that is required to approve the journal entry as part of the approval process may be identified. An approval from the at least one entity may be received. After receiving approval, the journal entry may be posted to the ledger such that the ledger indicates the credit or debit of the journal entry. Posting of the journal entry to the ledger may require no input from the user following receiving the request to post the journal entry to the ledger.

Abstract: A method of using rules to execute periodic allocations of funds in a hierarchal accounting structure may include receiving an allocation rule, comprising a source account, a rule for determining a first amount, a parent account, and an allocation basis; accessing a multidimensional data cube comprising a hierarchal arrangement and aggregated balances for each level of the hierarchal arrangement; generating an allocation scenario by allocating the first amount to the aggregated balances for the one or more child accounts according to the allocation rule; generating one or more accounting journal entries corresponding to the allocation scenario; posting the one or more accounting journal entries to a general ledger associated with a relational database; and updating, using the relational database, the multidimensional data cube to reflect the allocation scenario.

Abstract: A method of detecting variances in a plurality of accounts from different organizations within an Enterprise Financial Accounting system includes receiving a selection of a first account with an account type; receiving a selection of a first time interval and a second time interval; determining a first amount that is associated with the first account during the first time interval; determining a second amount that is associated with the first account during the second time interval; receiving a selection of a comparison operator that relates the first amount to the second amount; receiving a selection of a threshold; determining a comparison value by comparing the first amount to the second amount according to the comparison operator; determining that the comparison value violates the threshold according to the comparison operator; and displaying a first indication in a portal comprised of the first amount, the second amount, and the comparison value.

Abstract: In an embodiment, for any structural change that is made to a relational database, a corresponding change is also made to the multidimensional database. In an embodiment, the system determines that a particular structure is not implemented on the multidimensional database system. Based on metadata that defines the structure that is supposed to exist in the multidimensional database, the appropriate structure is created.

Abstract: In an embodiment, for any structural change that is made to a relational database, a corresponding change is also made to the multidimensional database. In an embodiment, the system determines that a particular structure is not implemented on the multidimensional database system. Based on metadata that defines the structure that is supposed to exist in the multidimensional database, the appropriate structure is created.