Financial Consolidation Model

Allow configurable decimal precision for journal entries to meet client requirements that require greater precision.

Support both division and multiplication methods for flexibility across implementations.

Add an option to select the translation method (monthly vs. YTD) to match different accounting policies.

Problem Statement: When the segment consolidation ledger is customised to use Balance Sheet cube instead of Balance Sheet (Segment) cube, journals do not pass data validation when segment-related fields are blank

Current Challenge: Troubleshooting/ tracking the data is nightmare Root Cause: When a user create a manual journal entry and try to post the journal system throws error message "Invalid" with balance constraint "Legal Entity" and allows to post ev...

The import folder for manual jourmal should allow subfolders so that journals from different departments can be placed in different folders. There is currently no option to navigate to subfolders in the import folder. The selection box in the "...

Extend the storage to capture reporting positions for the notes (text narratives and tabular information) which cannot be captured by the existing cubes. Provide sample data and reports for the most common notes sections.

Users would benefit from an easy way to set up custom data validations, similar to the setup of consolidation rules. E.g. the amount on a PnL Account needs to match a movement on a BS Account.

Sometimes, there are many Legal Entities at customers, paging function would be needed in reports: "Scope of consolidation", "Data collection", "Consolidation Manager", "Consolidated Financial Statement".

The Local GAAP element of the Consolidation dimension is the only element to receive original source data for the separate financial statements. This data is captured on the ~ element of the Scope dimension and shows automatically on all other sco...